-
Notifications
You must be signed in to change notification settings - Fork 13.4k
no MIR available for DefId #84455
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
Comments
While regression itself is related to the introduction of CTFE MIR, it seems this actually never worked correctly, with |
Assigning priority as discussed as part of the Prioritization Working Group procedure and removing @rustbot label -I-prioritize +P-medium |
I can't reproduce with the latest nightly and cargo. $ cargo build --verbose
Fresh ice_test v0.1.0 (/home/habbasi/bisect/ice_test)
Compiling bisect v0.1.0 (/home/habbasi/bisect)
Running `rustc --crate-name bisect --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=dffb54c3af23b7e8 -C extra-filename=-dffb54c3af23b7e8 --out-dir /home/habbasi/bisect/target/debug/deps -C incremental=/home/habbasi/bisect/target/debug/incremental -L dependency=/home/habbasi/bisect/target/debug/deps --extern ice_test=/home/habbasi/bisect/target/debug/deps/libice_test-e9c2aad897dc9d25.rlib`
error: language item required, but not found: `eh_personality`
error: aborting due to previous error
error: could not compile `bisect`
Caused by:
process didn't exit successfully: `rustc --crate-name bisect --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=dffb54c3af23b7e8 -C extra-filename=-dffb54c3af23b7e8 --out-dir /home/habbasi/bisect/target/debug/deps -C incremental=/home/habbasi/bisect/target/debug/incremental -L dependency=/home/habbasi/bisect/target/debug/deps --extern ice_test=/home/habbasi/bisect/target/debug/deps/libice_test-e9c2aad897dc9d25.rlib` (exit status: 1) Are there any further instructions for reproducing this? |
Apologies, forgot to mention you'll need to add [profile.dev]
panic = "abort"
[profile.release]
panic = "abort" Or build for a target that does not have panic unwinding enabled by default. |
(discussed in T-compiler meeting. This is an issue on stable, and might get a backport via #84549. Re-opening to investigate details of what worked, what stopped working, what is fixed, and what is still broken.) |
In the case reported here, one crate references In 1.50 static is non-reachable and codegenned locally. The change seems safe for backporting to me. |
Issue: rust-lang/rust#84455
Issue: rust-lang/rust#84455
Closing as the backport was declined. |
I couldn't I couldn't produce a single file example, as it seems the ICE is triggered when cross crate compilation is involved; i.e dumping the contents of lib.rs into test.rs does not trigger the ICE. This seems like a regression of the
const-fn
feature as this previously worked on nightly of the 1.50 stable release.Code
lib.rs
:test.rs
:Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: