Skip to content
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

ICE in qualify_consts.rs #66016

Closed
GabrielMajeri opened this issue Nov 1, 2019 · 3 comments · Fixed by #66047
Closed

ICE in qualify_consts.rs #66016

GabrielMajeri opened this issue Nov 1, 2019 · 3 comments · Fixed by #66047
Assignees
Labels
E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ O-x86_32 Target: x86 processors, 32 bit (like i686-*)

Comments

@GabrielMajeri
Copy link
Contributor

I was working on fixing the build for the packed_simd crate. Sadly, I ran into an internal compiler error:

error: internal compiler error: src/librustc_mir/transform/qualify_consts.rs:1145: promotion candidate validation mismatches (see above)
thread 'rustc' panicked at 'Box<Any>', src/librustc_errors/lib.rs:925:9
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:77
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:61
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1028
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1412
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:65
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:50
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:188
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:205
  10: rustc_driver::report_ice
  11: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:468
...

The full backtrace and log is available here.

I'm afraid I do not have enough time right now to investigate the issue and get a minimal repro, but I've reported it here in the hopes someone can help.

@csmoe csmoe added E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ O-x86 labels Nov 1, 2019
@ecstatic-morse
Copy link
Contributor

cc @eddyb

@ecstatic-morse
Copy link
Contributor

This is almost certainly caused by #65946.

@ecstatic-morse ecstatic-morse self-assigned this Nov 2, 2019
@ecstatic-morse
Copy link
Contributor

ecstatic-morse commented Nov 2, 2019

Hmm, actually the author reported this ~3 days ago, and that PR should only be on the latest nightly. Maybe a side effect of rust-lang/stdarch#825 somehow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ O-x86_32 Target: x86 processors, 32 bit (like i686-*)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants