Repository navigation
ICE in rollup #94523
Copy link
Copy link
Closed
Labels
C-bugCategory: This is a bug.Category: This is a bug.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️T-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
Activity
- addedI-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️T-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.C-bugCategory: This is a bug.Category: This is a bug.
on Mar 2, 2022 I am able to reproduce the issue with this code and
rustc -Z unstable-options --check-cfg=names():macro_rules! aa { () => { fn gg() { #[cfg(crossbeam_loom)] { let _ = val; unimplemented!("loom does not support non-atomic atomic ops"); } } }; } fn main() { aa!(); }
And it's combination of #94433 ("introduce" the ICE, preexisting issue) and #94298 (trigger the lint which trigger the ICE).
Further reduced to:
fn main() { #[cfg(crossbeam_loom)] {} }
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️T-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.
ICE encountered in a rollup, will post more details when i trace it further: