-
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
--bless all mir-opt tests. #70721
--bless all mir-opt tests. #70721
Conversation
alloc0 (size: 3, align: 1) { | ||
66 6f 6f │ foo | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting outcome: the ty::Const
uses this, but it also gets pretty-printed, so the alloc0
isn't strictly necessary.
But at least the super-verbose comments do mention Scalar(alloc0+0)
, so at least for now it doesn't hurt.
digraph Mir_0_3 { | ||
graph [fontname="monospace"]; | ||
node [fontname="monospace"]; | ||
edge [fontname="monospace"]; | ||
label=<fn main() -> ()<br align="left"/>>; | ||
bb0__0_3 [shape="none", label=<<table border="0" cellborder="1" cellspacing="0"><tr><td bgcolor="gray" align="center" colspan="1">0</td></tr><tr><td align="left" balign="left">_0 = ()<br/></td></tr><tr><td align="left">goto</td></tr></table>>]; | ||
bb1__0_3 [shape="none", label=<<table border="0" cellborder="1" cellspacing="0"><tr><td bgcolor="gray" align="center" colspan="1">1</td></tr><tr><td align="left">resume</td></tr></table>>]; | ||
bb2__0_3 [shape="none", label=<<table border="0" cellborder="1" cellspacing="0"><tr><td bgcolor="gray" align="center" colspan="1">2</td></tr><tr><td align="left">return</td></tr></table>>]; | ||
bb0__0_3 -> bb2__0_3 [label=""]; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoa! I didn't even know mir-opt
tests could test for this.
I now wish GitHub could render this as a graph 😞.
This comment has been minimized.
This comment has been minimized.
8633383
to
4abacd3
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
src/test/mir-opt/address-of/rustc.address_of_reborrow.SimplifyCfg-initial.after.mir
Show resolved
Hide resolved
@@ -14,6 +14,8 @@ enum Test2 { | |||
E = 5, | |||
} | |||
|
|||
// EMIT_MIR rustc.main.UninhabitedEnumBranching.diff | |||
// EMIT_MIR rustc.main.SimplifyCfg-after-uninhabited-enum-branching.after.mir |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've seen this pattern a few times. I wonder if we should have a diff mode for "before Optimization X to after optimization Y"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should always use .diff
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I mean is to diff across multiple optimizations instead of just a single one.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
4abacd3
to
daca904
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
4bc1d00
to
bedab17
Compare
bedab17
to
d0e0f40
Compare
@bors r+ |
📌 Commit d0e0f40 has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
@bors p=1001 |
⌛ Testing commit d0e0f40 with merge cd6b5e409513f9076baea053dabb9b5e69b0e18c... |
💔 Test failed - checks-azure |
I can't easily tell if non-determinism/sensitivity to test conditions is the problem, or a rebase is needed. EDIT: oh I was missing this (emphasis mine):
EDIT2: likely unwinding-related, we should probably just add this to the two tests: // ignore-wasm32-bare compiled with panic=abort by default |
@bors r=oli-obk |
📌 Commit 82d6e07 has been approved by |
deprioritising @bors p=1 |
☀️ Test successful - checks-azure |
r? @oli-obk