Skip to content

[ICE] librustc_traits/normalize_erasing_regions.rs:53: could not fully normalize #54114

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
WesleyAC opened this issue Sep 10, 2018 · 6 comments
Closed
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. 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) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@WesleyAC
Copy link

I have the following ICE:

error: internal compiler error: librustc_traits/normalize_erasing_regions.rs:53: could not fully normalize `fn() -> usize {std::mem::size_of::<wire::arp::Body<<AD as device::arp::ArpDevice<P>>::HardwareAddr, P>>}`

The full output of cargo build with RUST_BACKTRACE=1 is attached. This looks like it could be a regression of #49685

This is for the repo at https://fuchsia-review.googlesource.com/c/garnet/+/194882 - you should be able to cd into bin/recovery_netstack/core/ and run cargo build to get this error.

cc: @cramertj and @cavedweller

@memoryruins memoryruins added the I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ label Sep 11, 2018
@robsmith11
Copy link

robsmith11 commented Oct 30, 2018

Not sure if related, but I get the same error when compiling nalgebra with the latest nightly and mir-opt-level=3 (using default mir-opt-level fixes it):

Compiling nalgebra v0.16.7
error: internal compiler error: librustc_traits/normalize_erasing_regions.rs:53: could not fully normalize `base::matrix_slice::SliceStorage<N, base::dimension::U3, base::dimension::U1, <base::matrix_array::MatrixArray<N, base::dimension::U4, base::dimension::U1> as base::storage::Storage<N, base::dimension::U4>>::RStride, <base::matrix_array::MatrixArray<N, base::dimension::U4, base::dimension::U1> as base::storage::Storage<N, base::dimension::U4>>::CStride>`                                                                                     
thread 'main' panicked at 'Box<Any>', librustc_errors/lib.rs:600:9

@cramertj cramertj added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Oct 30, 2018
@oli-obk oli-obk added the A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) label Apr 16, 2019
@oli-obk
Copy link
Contributor

oli-obk commented Apr 16, 2019

This is happening in const eval. I'll investigate.

@jonas-schievink jonas-schievink added the C-bug Category: This is a bug. label Aug 6, 2019
@bkchr
Copy link
Contributor

bkchr commented Sep 19, 2019

I'm not sure that this is the same problem, but I have found the following:

error: internal compiler error: src/librustc_traits/normalize_erasing_regions.rs:42: could not fully normalize `<[u8] as Test>::Type`

thread 'rustc' panicked at 'Box<Any>', src/librustc_errors/lib.rs:650:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
error: aborting due to previous error

See here for the code.

If I change fn test(data: <[u8] as Test>::Type); to fn test(data: <&[u8] as Test>::Type); to make the resolution work, it compiles without any problem.

Without the extern "C", it does not produce an ICE and prints the expected error message.

asomers added a commit to bfffs/bfffs that referenced this issue Oct 1, 2019
@JohnTitor JohnTitor added the E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example label May 23, 2020
@Noratrieb
Copy link
Member

The link to the reproduction seems to be dead.

@bkchr
Copy link
Contributor

bkchr commented Jul 1, 2023

If you mean my link above, it works for me. However, I don't see the ICE anymore.

@apiraino
Copy link
Contributor

Closing as it seems the ICE can't be reproduced anymore, no MCVE was provided.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) C-bug Category: This is a bug. 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) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

10 participants