-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Allow precompile of methods in different modules and methods w/ keyword arguments #23548
Labels
compiler:precompilation
Precompilation of modules
docs
This change adds or pertains to documentation
Comments
For reference, the current docs for
|
I think a solution would be the ability to save Julia's binary state , to be resumed in a later time. |
This is not a 1.0 blocker as far as I can tell... |
Questions have been addressed or are less relevant now than other open issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
compiler:precompilation
Precompilation of modules
docs
This change adds or pertains to documentation
I'm opening this w/ the intent to gather feedback/answers to some questions on
precompile
so we can update the docs.precompile
compiling? A function w/ a specific set of arguments, but what is it being compiled to? Lowered form? Post-inference? LLVM IR?precompile
throw an error if it can't actually compile a function for a given set of arguments? Just returning false is fine, but just wondering why not just throw an errorprecompile(sort, (Vector{Int64},))
, but it's just compiling the keyword-arg-generator function likeright? And since it seems the "under the hood" actual keyword methods have gensym-ed names, it wouldn't be possible to precompile those? Am I on the right track there?
call
convention on 0.6/0.7). The other strategy I've taken is doing a@profile
on the initial code run and seeing which lines immediately precede largeinference.jl
blocks. Sometimes it seems that precompiling those methods doesn't remove the need to do inference in them though; is that because there might be methods in Base/other modules that still need compiling? So can a method only be precompiled if all the methods it calls are precompiled too?The text was updated successfully, but these errors were encountered: