Closed Haaroon closed 9 months ago
@Haaroon could you please describe how can we reproduce the issue? Thank you.
I wonder if this is https://github.com/rust-lang/rust/issues/116332 which has already been fixed in latest nightly :thinking:
type alias impl trait is not stable though, so the reproducers will be at least different 🤔
Hmm right.
Alright, I found a way to reproduce the issue from this project's dependencies: building tantivy-0.21.1 in release mode is enough to trigger the ICE.
Some good news: it doesn't ICE on nightly, nor on beta.
I will work on bisecting the involved PRs to see what could need a stable backport.
@matthiaskrgr you had the right intuition: the change in #115759 impacted more than unstable code and caused this ICE (as well as many others of course), and was fixed by #116415. The repro is different from #116332 but the cause and fix are indeed the same.
yay, all the time staring at compiler crashes finally payed out!
Incredible: #116333.
lol, crap... We need a better tracking of what to beta backport at the right time :/
@Haaroon could you please describe how can we reproduce the issue? Thank you.
I beleive it was because i tried to build tantivy with the release flag with maturin
I also can't run anymore a project I used to. It now breaks with a similar error when compiling bevy-inspector-egui
v0.19.0. I'm on a macOS with M1.
error: internal compiler error: no errors encountered even though `delay_span_bug` issued
error: internal compiler error: broken MIR in Item(DefId(0:152 ~ bevy_inspector_egui[68b7]::bevy_inspector::ui_for_entity_components::{closure#3})) (after phase change to runtime-optimized) at bb5[4]:
Alias(Opaque, AliasTy { args: [ReErased, ReErased], def_id: DefId(0:2162 ~ bevy_inspector_egui[68b7]::restricted_world_view::{impl#3}::get_entity_component_reflect::{opaque#0}) }) does not have fields
The code is public if you'd like another repo to test it: https://github.com/danieldidiobalsamo/boids
Yeah #118025 showed the issue also happening on bevy_inspector_egui
.
Also seeing this issue on my own project. Here's it failing on a PR that's just fixing a couple of lints:
WG-prioritization assigning priority (Zulip discussion).
@rustbot label -I-prioritize +P-high
I ran into this building a Rust for Linux driver. That codebase is probably even more complicated than the other examples here, so I'm not sure how useful it is, but just in case, here's the tree: https://github.com/AsahiLinux/linux/tree/gpu/rust-1.74-ice . You have to build for ARM64, I can provide more instructions if needed.
The topmost commit in that branch works around the ICE. Reverting it causes it to come back.
@rustbot label -P-high +P-critical
Is there a minor release?
@freedit-dev Yes, there will be a 1.74.1 release to fix some issues (#118607).
We are trying to also backport in some form #116415 to fix this issue as well (if I'm connecting the dots correctly)
As I understand it, this should be fixed by the backports in the 1.74.1 release, but I'll label this as needs-test so we can make sure it doesn't regress in future.
The test is this repro https://github.com/rust-lang/rust/issues/116333#issuecomment-1745705014 and was added in https://github.com/rust-lang/rust/pull/116415#issuecomment-1749189835.
Closing as fixed.
Meta
Error output