-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when using DoublePrecision #106
Comments
Hmm, 218 is an invalid ptx error. I have added a new level of verbosity in the latest branch: if you pull and recompile, and set your Opt_InitializationParameters.verbosityLevel to 3 it should dump out a lot of extra information. If you put the output here I might be able to take a guess at what is going wrong. |
After pulling the latest branch I realized that I fiddled with the opt code in order to make it run. This might be the reason for this error. Running the minimal_graph_only test with single precision led to:
I modified the cudacompille call in util.t The output is attached to this post. /usr/local/cuda points to a cuda 7.5 installation. |
I believe this is some poor interaction between atomic double precision float adds and your version of nvvm. One workaround for now is to set pascalOrBetterGPU = false on line 127 of util.t, but this will make double precision atomics slow. The other, better, workaround, is to switch to CUDA 8.0, like in #99 . Though I don't know what errors you might run into there. |
At the moment I am using the terra binaries mentioned in the readme file. I assume I have to change the version as well when I am compiling with CUDA 8.0? I think I am going to stick with single precision for the time being. |
When enabling Double Precision I get:
What can I do to fix this problem?
The text was updated successfully, but these errors were encountered: