ICE: in visit, at rust/typecheck/rust-tyty-variance-analysis-private.h:168
Open
Nobody has claimed this yet.
bug
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
Code
Reduced
trait RegularExpression: {
type Text;
}
trait Execute: RegularExpression {}
struct FindCaptures<'t, R>(&'t R::Text) where R: Execute, ;
Original
trait RegularExpression: Sized {
type Text;
}
trait Execute: RegularExpression {
fn execute(&self) -> Self::Text;
}
impl<'c> Execute for ExecNoSyncStr<'c> {
fn execute(&self) -> u8 {
self.0.clone()
}
}
struct ExecNoSyncStr<'a>(&'a u8);
impl<'c> RegularExpression for ExecNoSyncStr<'c> {
type Text = u8;
}
struct FindCaptures<'t, R>(&'t R::Text) where R: Execute, R::Text: 't;
enum FindCapturesInner<'r, 't> {
Dynamic(FindCaptures<'t, ExecNoSyncStr<'r>>),
}
fn main() {}
Meta
1a91028
Error output
<output>
Backtrace
crab1: internal compiler error: in visit, at rust/typecheck/rust-tyty-variance-analysis-private.h:168
0x2c1ef7b internal_error(char const*, ...)
../../gcc/diagnostic-global-context.cc:787
0xb49f7d fancy_abort(char const*, int, char const*)
../../gcc/diagnostics/context.cc:1813
0x90f926 Rust::TyTy::VarianceAnalysis::VisitorBase<Rust::TyTy::VarianceAnalysis::Term>::visit(Rust::TyTy::PlaceholderType&)
../../gcc/rust/typecheck/rust-tyty-variance-analysis-private.h:168
0xe755a6 Rust::TyTy::VarianceAnalysis::GenericTyVisitorCtx::add_constraints_from_ty(Rust::TyTy::BaseType*, Rust::TyTy::VarianceAnalysis::Term)
../../gcc/rust/typecheck/rust-tyty-variance-analysis.cc:399
0xe78479 Rust::TyTy::VarianceAnalysis::VarianceVisitorCtx<Rust::TyTy::VarianceAnalysis::Term>::add_constraints_from_mutability(Rust::TyTy::BaseType*, Rust::Mutability, Rust::TyTy::VarianceAnalysis::Term)
../../gcc/rust/typecheck/rust-tyty-variance-analysis-private.h:74
0xe78479 Rust::TyTy::VarianceAnalysis::VisitorBase<Rust::TyTy::VarianceAnalysis::Term>::visit(Rust::TyTy::ReferenceType&)
../../gcc/rust/typecheck/rust-tyty-variance-analysis-private.h:118
0xe755a6 Rust::TyTy::VarianceAnalysis::GenericTyVisitorCtx::add_constraints_from_ty(Rust::TyTy::BaseType*, Rust::TyTy::VarianceAnalysis::Term)
../../gcc/rust/typecheck/rust-tyty-variance-analysis.cc:399
0xe768ad Rust::TyTy::VarianceAnalysis::GenericTyVisitorCtx::process_type(Rust::TyTy::ADTType&)
../../gcc/rust/typecheck/rust-tyty-variance-analysis.cc:247
0xe76939 Rust::TyTy::VarianceAnalysis::GenericTyPerCrateCtx::process_type(Rust::TyTy::ADTType&)
../../gcc/rust/typecheck/rust-tyty-variance-analysis.cc:131
0xe94d86 Rust::Resolver::TypeCheckItem::visit(Rust::HIR::TupleStruct&)
../../gcc/rust/typecheck/rust-hir-type-check-item.cc:244
0xe9190d Rust::Resolver::TypeCheckItem::Resolve(Rust::HIR::Item&)
../../gcc/rust/typecheck/rust-hir-type-check-item.cc:57
0xe9190d Rust::Resolver::TypeCheckItem::Resolve(Rust::HIR::Item&)
../../gcc/rust/typecheck/rust-hir-type-check-item.cc:43
0xe4c12b Rust::Resolver::TypeResolution::Resolve(Rust::HIR::Crate&)
../../gcc/rust/typecheck/rust-hir-type-check.cc:71
0xd11bcf Rust::Session::compile_crate(char const*)
../../gcc/rust/rust-session-manager.cc:763
../gccrs/build/gcc/crab1 bug.rs -frust-incomplete-and-experimental-compiler-do-not-use
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reduced example with gcc/crab1 using -frust-incomplete-and-experimental-compiler-do-not-use, then read rust/typecheck/rust-tyty-variance-analysis-private.h at line 168 and the callers in rust-tyty-variance-analysis.cc. Done means the example no longer triggers the reported internal compiler error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100