-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Regression in nightly: llvmcall with integer pointers is deprecated, use an actual pointer type instead
#55006
Comments
I think this is somewhere in a JuliaSIMD repo, so I reported it in JuliaSIMD/ThreadingUtilities.jl#51. But these packages seem to no longer be maintained, so I won't hope for a fix. But after all, a deprecation should not throw an Error Exception as I this case. |
My understanding is that packages doing explicit llvmcalls need to adapt, because this is an upstream change in llvm. |
The test log reveals that it's run with
|
This is not a regression, but an intentional change. Citing the linked PR:
Basically, In any case, |
It is not helpful to always have these failing for reasons beyond our control. For background information, see here: <JuliaLang/julia#55006>
It is not helpful to always have these failing for reasons beyond our control. For background information, see here: <JuliaLang/julia#55006>
It is not helpful to always have these failing for reasons beyond our control. For background information, see here: <JuliaLang/julia#55006>
In a few packages I've seen tests with Julia nightly failing with this error.
E.g. in this log for GenericCharacterTables.jl:
This has been going on for a few weeks there at least. I'll see if I can reproduce this locally, and if so, will try to bisect. At this point it looks to me as if this is a problem inside Julia, but of course it might be a problem in the package or some of its dependencies (several of which use
ccall
extensively, so who knows, perhaps something got corrupted). But I have no good idea how to debug this other than "try to find out in which Julia commit this started to behave differently" and hoping this will give a clue.But maybe someone else has an idea what might cause this or how one might go about debugging it...
The text was updated successfully, but these errors were encountered: