-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Normalize types and consts in MIR opts. #110714
Conversation
r? @oli-obk (rustbot has picked a reviewer for you, use r? to override) |
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
⌛ Trying commit 4fe5136 with merge 29598da8b5f9d3359d6c501b375cf0e4b89b4b87... |
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (29598da8b5f9d3359d6c501b375cf0e4b89b4b87): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
|
@bors r+ rollup |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#110255 (Suggest using integration tests for test crate using own proc-macro) - rust-lang#110514 (Remove `find_map_relevant_impl`) - rust-lang#110566 (Don't create projection ty for const projection) - rust-lang#110637 (Group some sections of our logs in github actions) - rust-lang#110706 (Add `intrinsics::transmute_unchecked`) - rust-lang#110714 (Normalize types and consts in MIR opts.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
@cjgillot can we also run the |
I thought it was already on by default 🤦. No reason we shouldn't. |
Reveal opaque types before drop elaboration fixes rust-lang#113594 r? `@cjgillot` cc `@JakobDegen` This pass was introduced in rust-lang#110714 I moved it before drop elaboration (which only cares about the hidden types of things, not the opaque TAIT or RPIT type) and set it to run unconditionally (instead of depending on the optimization level and whether the inliner is active)
Reveal opaque types before drop elaboration fixes rust-lang#113594 r? `@cjgillot` cc `@JakobDegen` This pass was introduced in rust-lang#110714 I moved it before drop elaboration (which only cares about the hidden types of things, not the opaque TAIT or RPIT type) and set it to run unconditionally (instead of depending on the optimization level and whether the inliner is active)
Reveal opaque types before drop elaboration fixes rust-lang/rust#113594 r? `@cjgillot` cc `@JakobDegen` This pass was introduced in rust-lang/rust#110714 I moved it before drop elaboration (which only cares about the hidden types of things, not the opaque TAIT or RPIT type) and set it to run unconditionally (instead of depending on the optimization level and whether the inliner is active)
Some passes were using a non-RevealAll param_env, which is needlessly restrictive in mir-opts.
As a drive-by, we normalize all constants, since just normalizing their types is not enough.