Closed raffian closed 2 years ago
I managed to get beyond this issue. Turned out my input file had Windows line endings (can't believe I'm even admitting to that, but whatever, it happens) Also, my source files are C, not CPP, not sure if that was causing CUBLAS_STATUS_NOT_INITIALIZED
but I intend to create a new processor for C.
closed
After updating NVIDIA driver to 510.06, CUDA is finally recognized.
Successfully compiled cuda extensions but had to comment out this section in apex to suppress a runtime error as per the output suggestion. This may (or may not) be the cause of
CUBLAS_STATUS_NOT_INITIALIZED
(see below).apex - commented out
Cuda Ext Compilation
Translation cpp --> Java Source lang file is C (not cpp), about 600 lines of code like this (nothing fancy):
python -m codegen_sources.model.translate Error: CUBLAS_STATUS_NOT_INITIALIZED
It's worth noting I haven't trained any models; just using
TransCoder_model_1.pth
as-is and doing a simple cpp->Java translation as a test. What is the significance of this error?RuntimeError: CUDA error: CUBLAS_STATUS_NOT_INITIALIZED when calling cublasCreate(handle)