-
Notifications
You must be signed in to change notification settings - Fork 187
Open
Labels
Description
auto-reduced (treereduce-rust):
//@compile-flags: -frust-incomplete-and-experimental-compiler-do-not-use
#![cfg(feature = feature)]
original:
#![cfg(feature = feature)]
Version information:
Possibly related line of code:
gccrs/gcc/rust/ast/rust-ast.cc
Lines 4034 to 4046 in 4db0cf7
} | |
bool | |
MetaItemPathExpr::check_cfg_predicate (const Session &session) const | |
{ | |
// FIXME: Accept path expressions | |
rust_assert (expr->is_literal ()); | |
return session.options.target_data.has_key_value_pair (path.as_string (), | |
expr->as_string ()); | |
} | |
std::vector<std::unique_ptr<Token>> | |
Token::to_token_stream () const |
Command:
/home/matthias/vcs/github/gccrs/gccrs-build/gcc/crab1 -frust-incomplete-and-experimental-compiler-do-not-use
Program output
crab1: internal compiler error: in check_cfg_predicate, at rust/ast/rust-ast.cc:4040
0x301e249 internal_error(char const*, ...)
../../gcc/diagnostic-global-context.cc:786
0xc22881 fancy_abort(char const*, int, char const*)
../../gcc/diagnostics/context.cc:1787
0x900a5d Rust::AST::MetaItemPathExpr::check_cfg_predicate(Rust::Session const&) const
../../gcc/rust/ast/rust-ast.cc:4040
0x900a5d Rust::AST::MetaItemPathExpr::check_cfg_predicate(Rust::Session const&) const
../../gcc/rust/ast/rust-ast.cc:4037
0xdf160c Rust::AST::Attribute::check_cfg_predicate(Rust::Session const&) const
../../gcc/rust/ast/rust-ast.cc:4196
0xeac38e Rust::CfgStrip::fails_cfg_with_expand(std::vector<Rust::AST::Attribute, std::allocator<Rust::AST::Attribute> >&) const
../../gcc/rust/expand/rust-cfg-strip.cc:75
0xeaee66 Rust::CfgStrip::visit(Rust::AST::Crate&)
../../gcc/rust/expand/rust-cfg-strip.cc:156
0xe7a118 Rust::Session::expansion(Rust::AST::Crate&, Rust::Resolver2_0::NameResolutionContext&)
../../gcc/rust/rust-session-manager.cc:943
0xe87165 Rust::Session::compile_crate(char const*)
../../gcc/rust/rust-session-manager.cc:618
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.