-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Cuda compile errors #12
Comments
at a quick glance i can see an error about unsupported old cuda
architecture. perhaps the gpu auto detection has failed. what gpu is on the
build machine, and is it the one you intend to use? anyway, you can set an
explicit gpu architecture as an environment variable before running cmake.
from the readme:
TCNN_CUDA_ARCHITECTURES enivonment variable for the GPU you would like to
use. Set it to 86 for RTX 3000 cards, 80 for A100 cards, and 75 for RTX
2000 cards.
let me know if that helps!
|
Ah I see. I'm trying to run this on an AWS ec2 instance and it has a K80 GPU. (there's only one GPU on the machine I'm trying this on so I thought I wouldn't need to specify the architecture) |
Unfortunately, both K80 and V100 GPUs are unsupported. This codebase requires at least compute capability 75+, which means RTX 2000-series GPUs, A100 GPUs, or RTX 3000-series GPUs. See also #13. I will momentarily update the README to reflect this more explicitly |
Apologies, but it's currently not in our scope to add dedicated implementations for older GPUs. In part, because earlier GPU's performance would benefit much less from a fully fused implementation due to them being more compute rather than memory-bound than newer GPUs on the small-MLP workload. All that said, I would still be more than happy to merge code contributions that improve compatibility. |
I'm getting errors when compiling by running
cmake --build build --config RelWithDebInfo -j 16
The build error log is long, so I put it here: https://pastebin.com/6tRsjYfM
Is this due to some incorrect cuda version incompatibility? I'm on cuda 11.2
The text was updated successfully, but these errors were encountered: