You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Missing ICE info after some compiler panics #105637
With the panic in ICE with mismatch in trait associated constant #105632, the output now ends immediately after the stack trace. The information about how to report an ICE is missing, and the query stack is also missing.
As an example, here's the post-stack-trace output when testing #105632 with an older build:
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: rustc 1.68.0-nightly (657eefe2d 2022-12-11) running on x86_64-apple-darwin
query stack during panic:
#0 [typeck] type-checking `bar`
#1 [typeck_item_bodies] type-checking all item bodies
#2 [analysis] running analysis passes on this crate
end of query stack
And we can see on the playground that the usual ICE post-trace output is missing.
Note that this ICE was not present on nightly-2022-10-24, and is most useful for bisecting on win/mac, not linux: the following example should be usable for that.
We can see the ICE is missing the post trace output on the current beta (1.66.beta.2) on the playground, and the output changed in nightly-2022-10-24, it is present in nightly-2022-10-23.
Since this is useful output for reporting issues, debugging and bisection, should we do something about ThinLTO landing on stable on linux in 2 days (e.g. disabling rust.lto=thin on the x64 linux dist builder on beta) ? I'm not sure anyone will have the time to investigate and land a fix by then.
Probably. The fix has landed on nightly and beta, but the PR is still stable-nominated. It's not really critical to do such a backport unless someone experiences issues on 1.66 or the triage WG sees too many bug reports they don't like.
As @lqd says - the stable backport was discussed but ultimately kept "on hold" to see how the patch behaves in the beta channel. A stable backport sometimes means a point release and that's up to T-infra to decide.
Ok if you prefer to close this issue, we can always re-open if a stable backport will be approved (that will be discussed probably next week)
Activity
jruderman commentedon Dec 12, 2022
Requesting prioritization because affects the quality of bug reports and may interfere with bisection.
@rustbot prioritize
compiler-errors commentedon Dec 12, 2022
@jruderman do you test on an x86_64 mac? otherwise, I'm curious how you bisected this to #103647.
jruderman commentedon Dec 12, 2022
Yes, this is all on x86_64 mac.
lqd commentedon Dec 13, 2022
I'm not sure why this would affect ICEs so I've posted the #105646 revert to allow time for some investigation.
Rollup merge of rust-lang#105646 - lqd:revert-thinlto, r=Mark-Simulacrum
lqd commentedon Dec 13, 2022
This issue isn't platform-specific, and happens on all nightlies built with ThinLTO:
x86_64-apple-darwin#103647 starting with nightly-2022-12-12 (being reverted in Revert "enable ThinLTO for rustc on x86_64-apple-darwin dist builds" #105646)Examples:
And we can see on the playground that the usual ICE post-trace output is missing.
Note that this ICE was not present on
nightly-2022-10-24, and is most useful for bisecting on win/mac, not linux: the following example should be usable for that.We can see the ICE is missing the post trace output on the current beta (1.66.beta.2) on the playground, and the output changed in
nightly-2022-10-24, it is present innightly-2022-10-23.Since this is useful output for reporting issues, debugging and bisection, should we do something about ThinLTO landing on stable on linux in 2 days (e.g. disabling
rust.lto=thinon the x64 linux dist builder on beta) ? I'm not sure anyone will have the time to investigate and land a fix by then.apiraino commentedon Dec 13, 2022
WG-prioritization assigning priority (Zulip discussion).
@rustbot label -I-prioritize +P-critical
Auto merge of rust-lang#105646 - lqd:revert-thinlto, r=Mark-Simulacrum
lqd commentedon Dec 17, 2022
#105800 should fix the
-Zdylib-ltobug causing this issue, so we shouldn't need to revert therust.lto = thinconfig on the dist builders.Auto merge of rust-lang#105800 - lqd:dylib-thinlto, r=bjorn3
Auto merge of rust-lang#105845 - lqd:revert-thinlto-revert, r=Mark-Si…
Noratrieb commentedon Dec 31, 2022
Can this be closed now?
lqd commentedon Dec 31, 2022
Probably. The fix has landed on nightly and beta, but the PR is still stable-nominated. It's not really critical to do such a backport unless someone experiences issues on 1.66 or the triage WG sees too many bug reports they don't like.
apiraino commentedon Dec 31, 2022
As @lqd says - the stable backport was discussed but ultimately kept "on hold" to see how the patch behaves in the beta channel. A stable backport sometimes means a point release and that's up to
T-infrato decide.Ok if you prefer to close this issue, we can always re-open if a stable backport will be approved (that will be discussed probably next week)
jyn514 commentedon Apr 27, 2023
This is several months old at this point, I think it's safe to say there won't be a stable backport 😄