-
-
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
export jl_resolve_globals_in_ir
#42013
Conversation
This would be very useful for external `AbstractInterpreter`s to infer (and possibly even optimize) toplevel thunks.
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
Sort of like with Cthulhu we could do a clean break, and indeed strive for a bit of unification between the two interpreters. It might make sense, though, to redesign the interpretation byte-code (e.g., JuliaDebug/JuliaInterpreter.jl#309) first. |
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note though that this has global side-effects, so you should only call it if you are executing the code.
Yeah, but that side-effects are already involved with method definitions, right ? |
Ah, and it looks like you can selectively disable them with setting |
Well there are also possibilities that |
Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
…ngs (#241) Better to work with <JuliaLang/julia#42013>, but I also added an hacky fallback that makes use of the existing method definition pipeline.
This would be very useful for external `AbstractInterpreter`s to infer (and possibly even optimize) toplevel thunks.
This would be very useful for external `AbstractInterpreter`s to infer (and possibly even optimize) toplevel thunks.
This would be very useful for external
AbstractInterpreter
sto infer (and possibly even optimize) toplevel thunks.
(like aviatesk/JET.jl#241)
/cc @timholy we may be able to use this to eliminate some special casings within JuliaInterpreter (like resolving toplevel
Symbol
s asGlobalRef
s). The code may end up being more complex on the contrary because of the compatibility with older Julia versions though.