-
Notifications
You must be signed in to change notification settings - Fork 35
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
expected return statement, got JuliaInterpreter.SSAValue(2) #288
Comments
|
What Julia version? If recent, please try master branch of JuliaInterpreter, may have been fixed by #286 |
1.1.1, but also happens on julia master (JuliaLang/julia@efd794e), also happens with JuliaInterpreter master (04d1fb5). |
Problematic call is here, it's a |
Ah okay. Yea, I had problems in the early days of the new JuliaInterpreter with SIMD.jl, but forgot about it. Here is an example, still with
|
That's probably good enough, we can make |
So, dup of #112? |
I just got this error again with [email protected] when running the original code. |
Drat. Forgot about this until today. I poked at it, and it's a world-age issue (it should work if you edit it a second time). The issue is that our tests run at top-level and hence the world age can update, whereas with Revise it's run from inside a function. I only see one option: when we define compiled handlers for llvmcall (and probably ccall), we may need to do something evil: extract the method tables and set the world age to that of the current running task. Thoughts, @KristofferC? (I know how to do that and will implement it if appropriate, I'm just wonder if it's something we can countenance.) |
I don't fully grok If you feel messing with world ages is the best we can do then let's go with that. |
Good question. I was worried we'd have to add it lots of places, but you prompted me to check again. Turns out we can fix it by making this line |
With the following (minified) package
I get the following when trying to revise the module:
Maybe there is something funky going on with
@pure
-usage inTensors.jl
? As noted, removing the multiplication solves the problem.The text was updated successfully, but these errors were encountered: