-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
A regression test for #115145 #118805
A regression test for #115145 #118805
Conversation
The Miri subtree was changed cc @rust-lang/miri Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I swear the tests passed locally, which I thought was odd... |
Oh great this only fails with debug=true |
Could not assign reviewer from: |
I assume that diff in the assertion is related to the ICE in the mir-opt test? That seems to be dataflow_const_prop calling the interpreter on dead code. Maybe Cc @cjgillot , seems like dataflow const prop is unfortunately still doing some things with the interpreter that shouldn't be possible. |
81c453d
to
3998ee9
Compare
Yes. I dropped the commit that was making the situation less clear. |
This comment has been minimized.
This comment has been minimized.
3998ee9
to
ace1fa8
Compare
Could not assign reviewer from: |
I've turned this PR into adding a regression test per #115145 (comment) I agree that keeping the assertion is better than removing it. |
Ah sorry only saw this now after I submitted rust-lang/miri#3225 which adds a similar test to Miri directly. |
I think it'd be good to also have the "futures" test though. Can you add this to That should probably be a Miri PR though. |
Closing in favor of rust-lang/miri#3226 |
Add a regression test for rust#115145 Per rust-lang/rust#118805 (comment)
Add a regression test for rust#115145 Per rust-lang#118805 (comment)
The example here (reduced from the crate deadpool) used to ICE Miri until the fix in #118871
r? @RalfJung