Closed
Description
These examples have been found on crater:
These reproduce with stage2
but not stage1
, unless stage0
is passed -Z orbit
, which means a compiler built by MIR trans will use more stack space than old trans did.
For procinfo
, there are just over 1000 frames, usually in the NodeIdAssigner
, my guess is that its AST has a depth 500-700 in places (it's using nom
, which might cause such extreme nesting).
cc @rust-lang/compiler
Metadata
Metadata
Assignees
Labels
Area: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.htmlCategory: This is a bug.Call for participation: Hard difficulty. Experience needed to fix: A lot.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Medium priorityRelevant to the compiler team, which will review and decide on the PR/issue.Performance or correctness regression from one stable version to another.