-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
bootstrap: Allow configuring the opt-level, not just debug vs release #112678
Comments
i'm going to use #112679 as a separate more broad issue for |
mentoring instructions: add this option to the Line 1679 in dcf3571
cargo.env(profile_var("OPT_LEVEL"), config.opt_level)
|
Can we confirm before we land this support that this is actually a significant win in practice? I recall historically having issues with optimize = false equivalents where the net effect is broken and slower tests - I would prefer to avoid landing support we don't want to actually support :) |
@Mark-Simulacrum this is especially useful in combination with #112679 - optimizing only rustc and not std should be a speedup even if we include the time taken for tests. |
@rustbot claim |
Maybe we should just generalize the |
Use RustOptimize to set optimize close rust-lang/rust#112678 Use RustOptimize to set optimize.
It would be nice if we could speed up stage1 library builds by building it with less opts and no debuginfo.
@jyn514 had the idea to control this with something like
rust.stage1.opt-level
The text was updated successfully, but these errors were encountered: