-
Notifications
You must be signed in to change notification settings - Fork 106
Add experimental jit mode integration to cargo #1066
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
Comments
So would this mean:
will:
|
No, in the JIT mode the rustc invocation that "builds" the executable actually JITs it and then immediately runs it. No executable is written to the disk. I did imagine that the cargo command would be |
Oh interesting, is it possible to share the majority of the dep tree (e.g., i have 400 crates) when jitting, so a modify source, cargo jit loop would be faster? And today, if i pass this flag to cargo cranelift and do cargo run, this won't do as you say above, right? It only currently works with explicit invocations of the cranelift using rustc, yes? |
Also, are there any plans to implement 2. I guess it's similar to adding something like a |
Currently only dylibs can be loaded by the JIT. I want to also make it work with rlibs though.
It will kinda work if you use your
I may attempt to integrate the Yorick meta tracer in the future. It does require explicit annotations about when to JIT what. It is also only meant to optimize language interpreters, not your average program. |
https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/jit.20support
The text was updated successfully, but these errors were encountered: