-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Not planned
Labels
C-bugCategory: This is a bug.Category: This is a bug.E-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleE-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.Call for participation: An issue has been fixed and does not reproduce, but no test has been added.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️O-windowsOperating system: WindowsOperating system: WindowsO-windows-msvcToolchain: MSVC, Operating system: WindowsToolchain: MSVC, Operating system: WindowsO-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)P-mediumMedium priorityMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Trying to compile winrt with latest nightly msvc got a internal compiler error.
error: internal compiler error: src\librustc_traits\normalize_erasing_regions.rs:42: could not fully
normalize `unsafe extern "system" fn(*mut rt::gen::windows::foundation::AsyncActionProgressHandler<TProgress>, *mut
rt::gen::windows::foundation::IAsyncActionWithProgress<TProgress>, <TProgress as
rt::RtType>::Abi) -> i32`
note: rustc 1.41.0-nightly (ded5ee001 2019-11-13) running on x86_64-pc-windows-msvc
note: compiler flags: -C debuginfo=2 --crate-type lib
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
#0 [normalize_ty_after_erasing_regions] normalizing `ParamEnvAnd { param_env: ParamEnv { caller_bounds: [], reveal: All, def_id: None }, value: unsafe extern "system" fn(*mut rt::gen::windows::foundation::AsyncActionProgressHandler<TProgress>, *mut rt::gen::windows::foundation::IAsyncActionWithProgress<TProgress>, <TProgress as rt::RtType>::Abi) -> i32 }`
#1 [lint_mod] linting module `rt::gen::windows::foundation`
#2 [analysis] running analysis passes on this crate
end of query stack
Saw similar error over with this one: #64908 so figured I would report here and not in the winrt github. Project compiles fine with latest stable on x86-64-pc-windows-msvc
.
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.E-needs-mcveCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleCall for participation: This issue has a repro, but needs a Minimal Complete and Verifiable ExampleE-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.Call for participation: An issue has been fixed and does not reproduce, but no test has been added.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️O-windowsOperating system: WindowsOperating system: WindowsO-windows-msvcToolchain: MSVC, Operating system: WindowsToolchain: MSVC, Operating system: WindowsO-x86_64Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)P-mediumMedium priorityMedium priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
Centril commentedon Nov 14, 2019
Can you please provide a backtrace, and if possible, a minimal reproducer? Thanks.
cc @wesleywiser
pnkfelix commentedon Nov 14, 2019
also, I think this is the winrt repo: https://github.com/contextfree/winrt-rust
pnkfelix commentedon Nov 14, 2019
triage: P-high for now. Removing nomination.
basil-cow commentedon Nov 14, 2019
I was able to reproduce it,
tensor-programming commentedon Nov 16, 2019
Yeah, sorry, haven't been on this machine for a few days. Areredify's backtrace looks right compared to what I saw before.
Heres the full backtrace just in case.
wesleywiser commentedon Mar 14, 2020
Using
cargo-bisect-rustc
, I discovered that this was fixed two days later innightly-2019-11-15
. It looks like #66378 was responsible for fixing this.pnkfelix commentedon Mar 19, 2020
closing as fixed by PR #66378
pnkfelix commentedon Mar 19, 2020
@wesleywiser points out this may need a regression test. Reopening, re-prioritizing as P-medium and marking E-needstest.
Enselic commentedon Sep 8, 2023
Triage: I agree it would be good to have a regression test for the ICE. But now, more than three years later, I think we have to accept that no one will write a regression test. Had there been a minimal reproducer, I would have written a regression test myself. But by now it simply is too much effort to figure out how to reproduce and figure out how to minimize the reproducer.
There are 3595 other C-bugs open in this repo (of which 584 are I-ICE and 113 are E-needs-test) that deserves more attention than this issue, and there will always be issues that deserves more attention than this issue. Let's close this.