-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Load-bearing comment Incremental ICE #93602
Comments
If I had to guess, #93066 seems very relevant as what could've fixed this. the blamed line:
Contextrust/compiler/rustc_query_impl/src/on_disk_cache.rs Lines 694 to 731 in 0426998
Currentrust/compiler/rustc_query_impl/src/on_disk_cache.rs Lines 683 to 720 in 27f5d83
The reason for it to not panic anymore isn't localized here, so I can't track it down. cc @nnethercote, any ideas what could've caused this change? |
I can't see how #93066 would affect this. The only likely behavioural changes that PR would cause is that if problems occurred with metadata decoding (e.g. corrupted metadata) then rustc would panic a bit earlier than it did previously. @Aaron1011 You've been looking a lot at incremental issues lately, any ideas about this one? |
I don't think this is caused by the comment itself, but by the change in line numbers triggered by adding/removing lines. |
It does seem to be due to span data changing, but it's interesting in how inconsistent it is; changes in some places are fine, and some aren't. (And if you're keeping it rustfmtd, it translates to load bearing comments keeping it from reformatting into an ICE.) In any case, this has been incidentally fixed (suppressed?) by changes between beta and nightly, so I don't know how much investigation this is actually worth. At least it's an ICE rather than a miscomp. Incremental issues spook me. |
Given that this no longer occurs, I'm going to go ahead and close this. |
This is as minimized as I could get:
Code
cargo build
cargo build
Meta
This is not happening on nightly. But load bearing comments is scary enough I wanted to report this anyway.
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: