Revert "Apply EarlyOtherwiseBranch to scalar value #129047"#130775
Revert "Apply EarlyOtherwiseBranch to scalar value #129047"#130775bors merged 2 commits intorust-lang:masterfrom
Conversation
…h_scalar, r=cjgillot" This reverts commit a772336, reversing changes made to 702987f. It seems Apply EarlyOtherwiseBranch to scalar value rust-lang#129047 may have lead to several nightly regressions: - rust-lang#130769 - rust-lang#130774 - rust-lang#130771 And since this is a mir-opt ICE that seems to quite easy to trigger with real-world crates being affected, let's revert for now and reland the mir-opt later.
|
r? @chenyukang rustbot has assigned @chenyukang. Use |
|
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt |
|
r? @rust-lang/wg-mir-opt |
|
Could you perhaps add a regression test (in a separate commit)? |
(I did just before you asked lol) |
|
@bors r+ p=1 Fixing a critical regression, should land ASAP. |
Revert "Apply EarlyOtherwiseBranch to scalar value rust-lang#129047" This reverts PR rust-lang#129047, commit a772336, reversing changes made to 702987f. cc `@DianQK` and `@cjgillot` as the PR author and reviewer of rust-lang#129047 respectively. It seems [Apply EarlyOtherwiseBranch to scalar value rust-lang#129047](rust-lang#129047) may have lead to several nightly regressions: - rust-lang#130769 - rust-lang#130774 - rust-lang#130771 Example test that would ICE with changes in rust-lang#129047 (this test is included in this PR): ```rs //@ compile-flags: -C opt-level=3 //@ check-pass use std::task::Poll; pub fn poll(val: Poll<Result<Option<Vec<u8>>, u8>>) { match val { Poll::Ready(Ok(Some(_trailers))) => {} Poll::Ready(Err(_err)) => {} Poll::Ready(Ok(None)) => {} Poll::Pending => {} } } ``` Since this is a mir-opt ICE that seems to quite easy to trigger with real-world crates being affected, let's revert for now and reland the mir-opt after these are fixed.
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
|
@bors retry (spurious network error) |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (67bb749): comparison URL. Overall result: ❌✅ regressions and improvements - ACTION NEEDEDNext Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression 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)Results (primary -4.0%, secondary 3.7%)This 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.
CyclesResults (primary -0.6%)This 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.
Binary sizeResults (primary -0.4%, secondary -0.0%)This 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.
Bootstrap: 769.56s -> 767.328s (-0.29%) |
|
This is a revert, no investigation needed. @rustbot label: +perf-regression-triaged |
Update Rust toolchain from nightly-2024-09-23 to nightly-2024-09-25 without any other source changes. We skip over 2024-09-24 as that version ICEs when trying to build http-body (fixed by rust-lang/rust#130775). --------- Co-authored-by: celinval <35149715+celinval@users.noreply.github.com> Co-authored-by: Michael Tautschnig <tautschn@amazon.com>
This reverts PR #129047, commit a772336, reversing changes made to 702987f.
cc @dianqk and @cjgillot as the PR author and reviewer of #129047 respectively.
It seems Apply EarlyOtherwiseBranch to scalar value #129047 may have lead to several nightly regressions:
Example test that would ICE with changes in #129047 (this test is included in this PR):
Since this is a mir-opt ICE that seems to quite easy to trigger with real-world crates being affected, let's revert for now and reland the mir-opt after these are fixed.