-
Notifications
You must be signed in to change notification settings - Fork 63
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
Missing invoke handling causes infinite loop #1134
Comments
|
|
Hm can't reproduce locally. It was crashing on 1.10-beta, but is passing for me on rc1. |
Even trying to directly reconstruct the call:
|
So after a short investigation. The code behaves properly outside the test-suite. It is not clear why this recurses to begin with. |
This reproduces in a file for me:
I think I know what is happening and why, but not immediately a good fix. Right now applylatest/applygeneric/invoke all become a applygeneric on runtime_generic_augfwd. However, in 1.10 the first call above becomes a jl_invoke(hvcat, ....) to a specialized method for all args. That jl_invoke becomes a call to autodiff hvcat(all those args). Once again the julia compiler decides to wrap that inside of a jl_invoke, instead of doing the specialized one, creating the loop. |
In my opinion the best solution is for us to pass the mi down to thunk, but we cannot since a generated method cannot take a methodinstance in a val [which I know concerns you for other reasons, but thats my immediate thoughts fo what blocks] |
This PR does a partial fix but hits a julia issue I don't understand with gpucompiler.jl: #1169 Specifically the outermost function is this, which has a vararg at the end and has a different julia calling abi:
Could gpucompiler give us one with the usual ABI?
|
@vchuravy it looks like in get_function_name of codegen.cpp, the specsig flag, which should be set to true by gpucompiler is getting ignored or overridden or something |
1 similar comment
Can you expand on this? Who is the caller? Is |
So the culprit is that we are not handling the
which got backported to |
See CI on 1.10 cc @vchuravy @gbaraldi
The text was updated successfully, but these errors were encountered: