-
Notifications
You must be signed in to change notification settings - Fork 176
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
compile failed while use opt-level=3 after updating to rust 1.74 #163
Comments
same here but on windows note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T- note: rustc 1.74.0 (79e9716c9 2023-11-13) running on x86_64-pc-windows-msvc note: compiler flags: --crate-type lib -C opt-level=3 -C embed-bitcode=no -C debuginfo=2 -C debug-assertions=on note: some of the compiler flags provided by cargo are hidden query stack during panic: |
I'm also getting this error on Linux, while compiling a Bevy project that depends on
|
I'll try to make a more minimal reproduction later and bisect rustc and submit a bug report for this (unless somebody wants to beat me to it) |
Something pretty weird is going on, I can reproduce this when explicitly depending on the crates.io version. Compiling in the repo or depending on it via Also in |
regression was in rust-lang/rust@c545019 (rust-lang/rust#115759) |
the issue is marked as |
When building on Rust 1.74, [this] happens. Until a fix is released (via 1.74.1 or similar) building on opt-level = 3 will cause an ICE to occur. [this]: jakobhellermann/bevy-inspector-egui#163
1. Update Bevy to 0.12 2. Update related deps ( ggrs, bevy_ggrs, matchbox, etc. ) 3. Log warning if winit cannot find main window to avoid panic - I don't understand why this changed see below. 4. Switch to `1.72` toolchain due to Rust compiler regression. ### Winit Panic Some new issue was introduced with the Bevy 0.12 upgrade, this line started panicking, so we just log a warning and abort if we can't get the primary window. https://github.com/mikeder/turtletime/pull/3/files#diff-42cb6807ad74b3e201c5a7ca98b911c5fa08380e942be6e4ac5807f8377f87fcL83 NiklasEi/bevy_game_template#80 ### Compiler Regression I was unable to compile `bevy-egui-inspector` after updating to Rust to the 1.74 toolchain, it turns out there was a compiler regression so I've pinned my toolchain to 1.72 ( there was [another regression](rust-lang/rust#117545) in 1.73 that sounds nasty enough to avoid for now too ) jakobhellermann/bevy-inspector-egui#163 rust-lang/rust#117976 #### Segmentation Fault Originally I tried to use the `nightly` toolchain as recommended in the above `bevy-egui-inspector` issue, but when I did, my game instantly crashed with a segmentation fault. I tried to use the [sanitizer](https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html) features to debug it, but the game compiled and ran just fine with the sanitizer flags. Ultimately I just downgraded to `1.72` and moved on with my life.
for reference of whoever finds this:
works as a workaround |
Rust 1.74.1 was released. |
Can confirm that 1.74.1 fixed the issue. |
I can also confirm it is fixed with |
I can also confirm it is fixed with 1.74.1. |
This is error message:
bevy-inspector-egui-0.21.0/src/bevy_inspector/mod.rs:415:17
|
415 | set_changed();
| ^^^^^^^^^^^
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.74.0 (79e9716c9 2023-11-13) running on aarch64-apple-darwin
note: compiler flags: --crate-type lib -C opt-level=3 -C embed-bitcode=no -C debuginfo=2 -C split-debuginfo=unpacked -C debug-assertions=on
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
end of query stack
error: could not compile
bevy-inspector-egui
(lib)The text was updated successfully, but these errors were encountered: