public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104668] New: [12 Regression] ICE in lookup_attribute_spec, at attribs.cc:425 Date: Wed, 23 Feb 2022 17:59:16 +0000 [thread overview] Message-ID: <bug-104668-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104668 Bug ID: 104668 Summary: [12 Regression] ICE in lookup_attribute_spec, at attribs.cc:425 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20220123 and 20220130 : (derived from g++.dg/cpp0x/lambda/lambda-variadic15.C) $ cat z1.cc template <class... Ts> void sink(Ts...); template <class... Ts> void f(Ts...) { sink([] { struct alignas:Ts) S {}; }...); } } int main() { f(0); } $ g++-12-20220220 -c z1.cc z1.cc: In lambda function: z1.cc:5:20: internal compiler error: Segmentation fault 5 | sink([] { struct alignas:Ts) S {}; }...); } | ^~~~~~~ 0xda25ef crash_signal ../../gcc/toplev.cc:322 0x89f4f1 lookup_attribute_spec(tree_node const*) ../../gcc/attribs.cc:425 0x75217e is_late_template_attribute ../../gcc/cp/decl2.cc:1243 0x75217e splice_template_attributes(tree_node**, tree_node*) ../../gcc/cp/decl2.cc:1340 0x752b1e cplus_decl_attributes(tree_node**, tree_node*, int) ../../gcc/cp/decl2.cc:1662 0x7eabc8 cp_parser_class_head ../../gcc/cp/parser.cc:26646 0x7eabc8 cp_parser_class_specifier_1 ../../gcc/cp/parser.cc:25824 0x7eb670 cp_parser_class_specifier ../../gcc/cp/parser.cc:26204 0x7eb670 cp_parser_type_specifier ../../gcc/cp/parser.cc:19348 0x7ec1a6 cp_parser_decl_specifier_seq ../../gcc/cp/parser.cc:15911 0x7ecd61 cp_parser_simple_declaration ../../gcc/cp/parser.cc:15159 0x7ee769 cp_parser_declaration_statement ../../gcc/cp/parser.cc:14367 0x7eed6b cp_parser_statement ../../gcc/cp/parser.cc:12452 0x7efcb4 cp_parser_statement_seq_opt ../../gcc/cp/parser.cc:12856 0x7efd6f cp_parser_compound_statement ../../gcc/cp/parser.cc:12808 0x7f0778 cp_parser_function_body ../../gcc/cp/parser.cc:25062 0x7f0778 cp_parser_lambda_body ../../gcc/cp/parser.cc:11799 0x7f0778 cp_parser_lambda_expression ../../gcc/cp/parser.cc:11118 0x7f0778 cp_parser_primary_expression ../../gcc/cp/parser.cc:5700 0x7f3725 cp_parser_postfix_expression ../../gcc/cp/parser.cc:7652
next reply other threads:[~2022-02-23 17:59 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-23 17:59 gscfq@t-online.de [this message] 2022-02-23 19:36 ` [Bug c++/104668] " mpolacek at gcc dot gnu.org 2022-02-24 15:36 ` marxin at gcc dot gnu.org 2022-04-06 15:55 ` cvs-commit at gcc dot gnu.org 2022-04-08 16:49 ` jakub at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-104668-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).