rust/src/test/mir-opt/simplify_try.try_identity.SimplifyArmIdentity.diff, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2022-11-01T04:45:41+00:00Detect unused files in `src/test/mir-opt` and error on them in tidy.2022-11-01T04:45:41+00:00Jakob Degenjakob.e.degen@gmail.com2022-10-31T00:17:25+00:00urn:sha1:17395b45b102b365e6fb19796223d190b5f2bebfAuto merge of #99762 - Nilstrieb:unreachable-prop, r=oli-obk2022-08-22T20:28:16+00:00borsbors@rust-lang.org2022-08-22T20:28:16+00:00urn:sha1:015a824f2dffe32707fceb59c47effaf7b73486c
UnreachableProp: Preserve unreachable branches for multiple targets
Before, UnreachablePropagation removed all unreachable branches. This was a pessimization, as it removed information about reachability that was used later in the optimization pipeline.
For example, this code
```rust
pub enum Two { A, B }
pub fn identity(x: Two) -> Two {
match x {
Two::A => Two::A,
Two::B => Two::B,
}
}
```
basically has `switchInt() -> [0: 0, 1: 1, otherwise: unreachable]` for the match. This allows it to be transformed into a simple `x`. If we remove the unreachable branch, the transformation becomes illegal.
This was the problem keeping `UnreachablePropagation` from being enabled, so we can enable it now.
Something similar already happened in #77800, but it did not show a perf improvement there. Let's try it again anyways!
Fixes #68105, although that issue has been fixed for a long time (see #77680).
bless mir-opt tests2022-08-22T13:19:40+00:00Nilstrieb48135649+Nilstrieb@users.noreply.github.com2022-07-29T16:52:38+00:00urn:sha1:5d7ce21b6ba31e93d7d9af71dd330ecc71387a2dbless mir-opt tests2022-08-21T19:21:46+00:00Nilstrieb48135649+Nilstrieb@users.noreply.github.com2022-07-26T13:17:02+00:00urn:sha1:18bfcd374fac5e65a9559771cbbb800d53b8549dbless mir opt tests2022-07-28T12:24:44+00:00Nilstrieb48135649+Nilstrieb@users.noreply.github.com2022-07-27T18:47:42+00:00urn:sha1:11c0280798da8f4d65dec25764237d2354e65273Fix tests broken by deaggregation change2022-04-11T13:26:26+00:00Jakob Degenjakob.e.degen@gmail.com2022-04-05T23:02:57+00:00urn:sha1:2a040284a5bc3bee1e78a7bea60e15a0033ef2b5Only create a single expansion for each inline integration.2022-02-27T18:05:56+00:00Camille GILLOTgillot.camille@gmail.com2022-02-27T15:09:52+00:00urn:sha1:e77e4fcf898ca4b2aa2041d2cbac200ed0f11b5bFix debugger stepping behavior around `match` expressions2021-08-25T19:17:22+00:00Wesley Wiserwesleywiser@microsoft.com2021-07-23T22:55:36+00:00urn:sha1:0a42dfc2fa2b373aedf7a169da3f0ec0e996fc9f
Previously, we would set up the source lines for `match` expressions so
that the code generated to perform the test of the scrutinee was matched
to the line of the arm that required the test and then jump from the arm
block to the "next" block was matched to all of the lines in the `match`
expression.
While that makes sense, it has the side effect of causing strange
stepping behavior in debuggers.
I've changed the source information so that all of the generated tests
are sourced to `match {scrutinee}` and the jumps are sourced to the last
line of the block they are inside. This resolves the weird stepping
behavior in all debuggers and resolves some instances of "ambiguous
symbol" errors in WinDbg preventing the user from setting breakpoints at
`match` expressions.
mir-opt & codegen test updates2021-05-06T18:37:45+00:00Scott McMurrayscottmcm@users.noreply.github.com2021-04-26T05:02:48+00:00urn:sha1:47b99485a391e21caf3e0312969ed00ccbc6c167
`SimplifyArm` and such are currently in `-Zunsound-mir-opts` and thus weren't running by default, so having something like them for the new desugar shouldn't be necessary for switching.
path trimming: ignore type aliases2021-02-06T10:03:48+00:00Dan Alonialonid@gmail.com2021-01-28T16:01:36+00:00urn:sha1:eaefe4a230d7c32d7c99da437ee8b87860f28704