-
-
Notifications
You must be signed in to change notification settings - Fork 83
SegFault for some getindex calls #38
Comments
The |
Is there any 0.6 that is supported? How do I build LLVM with assertions
enabled?
…On Sat, Dec 2, 2017 at 4:46 PM Tim Besard ***@***.***> wrote:
The warning: ignoring debug info with an invalid version (0) in error is
because you're running from release-0.6, which isn't supported, but
shouldn't break anything. I don't have time to look into it right now, but
you could building LLVM with assertions enabled.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#38 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABvNpv167NQVRY2eFrz4TLmD48-U0r4nks5s8VTSgaJpZM4QzTVj>
.
|
That snippet gives me CUDA illegal memory access error, https://gist.github.com/ilkerkesen/c921d41894b8667d8acc6e71803f04fe |
I think the answer to my second question is: https://llvm.org/docs/CMake.html |
Do build LLVM with assertions enabled you create
And the you purge you need to reconfigure your LLVM build or just do a 0.6.0 should work fine. |
0.6.0 is supported, 0.6.1 can be buggy. 0.6.2 will be supported, but @denizyuret your code triggers an assertion in a Julia pass:
I'll try to investigate next week. Might be caused by CUDAnative generating invalid IR (possibly only invalid with regard to the design of Julia's codegen and passes, undocumented requirements etc). |
But these don't come up in GPUArrays.jl's implementation, right? So just removing the CuArrays kernel should fix this? |
I can confirm that as @SimonDanisch suggested commenting out https://github.com/JuliaGPU/CuArrays.jl/blob/master/src/CuArrays.jl#L13, i.e. include("indexing.jl") stopped the error and now the test runs fine. |
Closed with 00276e3, see also JuliaGPU/GPUArrays.jl#90. |
Please see denizyuret/Knet.jl#198.
The text was updated successfully, but these errors were encountered: