-
Notifications
You must be signed in to change notification settings - Fork 227
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
Support for Jetson Nano and TX2 NX (CUDA 10.2) #2147
Comments
Testing GPUCompiler (at version 0.25.0) fails in a different way:
|
The GPUCompiler failure is a test timeout, and doesn't point to an actual issue.
That's your problem. You're using a beta release of Julia, so you should expect to have to use the latest versions of GPUCompiler.jl and friends for compatibility. |
Right - I was also mostly filing this issue to make a note of the status - if it was relevant to bringing CUDA 10.2 support to CUDA.jl v5. |
On a side note - running with the local toolkit fails to find
|
IIRC compute-sanitizer was only added in 11.0, it used to be memory-sanitizer. I guess we can make it optional again. |
Right - there's neither a cuda-sanitizer to be found via APT, nor a file mentioned in the build log for aarch64-linux-gnu: https://buildkite.com/julialang/yggdrasil/builds/6373#018b9530-dfb8-4278-85e1-fe37fd85c0ec |
Sorry, the old tool was called |
CUDA.jl now uses [email protected], which includes support for CUDA 10.2 again. I'll leave the updates to CUDA.jl itself to somebody with such hardware, though. |
WIP:
Miscellaneous notes
Non-bug report regarding running tests on an unreasonable configuration:
Describe the bug
Testing CUDA.jl v4.0.1 on aarch64-linux-gnu fails with stack:
GPUCompiler is at version 0.17.3.
GPUCompiler tests
Testing GPUCompiler fails on the same assertion.
Testing GPUCompiler (at version 0.25.0) fails in a different way (see first comment).
To reproduce
The Minimal Working Example (MWE) for this bug:
Manifest.toml
Expected behavior
Tests pass.
Version info
Details on Julia:
Details on CUDA:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: