You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a program using LoopVectorization, in VS Code with Julia extension 1.4.3, I get this when I start debug mode, referencing line 340 of stridedpointers.jl (@generated function $f(p1::Core.LLVMPtr{T,0}, p2::Core.LLVMPtr{T,0}) where {T})
I'm sorry I don't know enough about Julia to understand and answer this question. The program runs fine out of debug mode. (Or if I comment out the @tturbo reference in the function higher up in the call stack.) I'm happy to perform any tests I can understand, like a sample usage of llvmcall.
Not that I recall, sorry. I ended up reluctantly dropping @turbo from my project because it is intended for interactive use and @turbo was adding a lot to initial load time.
For a program using LoopVectorization, in VS Code with Julia extension 1.4.3, I get this when I start debug mode, referencing line 340 of stridedpointers.jl (
@generated function $f(p1::Core.LLVMPtr{T,0}, p2::Core.LLVMPtr{T,0}) where {T}
)[stack trace continues, referencing my code]
Results from typing status in the package manager:
The text was updated successfully, but these errors were encountered: