-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Regression in -Z dump-mir=all #41697
Comments
Last working nightly: |
maybe it was #41368 ? cc @nikomatsakis |
could be. let me try it on my big MIR refactoring branch =) |
Yes. I can reproduce. Will investigate. |
I see the problem. PR coming soon. |
Fix at #41777 |
…elb1 dump-mir was causing cycles by invoking item-path-str at bad times Workaround for now, but probably a better fix is to opt **in** to using the types for impls (if we do that at all; maybe filename/line is better). Fixes #41697
I'm still seeing this issue, on the latest nightly and on master. |
@dwrensha can you give more details of how you are reproducing the problem? (I added a test for the precise scenario reported, so I'm reasonably sure it's not that case anymore.) |
|
Hmm, perhaps my regression test wasn't sufficient. I see I used |
The earliest commit where I can reproduce this problem is 2cca256. |
avoid cycles in mir-dump, take 2 This fixes rust-lang#41697, for real this time, but I'm not sure how best to add a regression test. I was considering maybe adding some flag so that the MIR dumping doesn't actually get written to files (e.g., overloading the directory flag so you can specify nil or something). cc @dwrensha @oli-obk
running
rustc -Z dump-mir=all src/test/run-pass/issue-33387.rs
yields
Happening on
rustc 1.19.0-nightly (777ee2079 2017-05-01)
. Did not happen on the latest nightly available through rustup on 27.04.2017.The text was updated successfully, but these errors were encountered: