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++/104623] New: [11/12 Regression] ICE in cp_parser_skip_to_pragma_eol, at cp/parser.cc:4107 Date: Mon, 21 Feb 2022 21:29:59 +0000 [thread overview] Message-ID: <bug-104623-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104623 Bug ID: 104623 Summary: [11/12 Regression] ICE in cp_parser_skip_to_pragma_eol, at cp/parser.cc:4107 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 20200712 and 20200719 : $ cat z1.cc void f () { struct __attribute__() a #pragma omp task } $ g++-12-20220220 -c z1.cc -fopenmp z1.cc: In function 'void f()': z1.cc:5:1: internal compiler error: in cp_parser_skip_to_pragma_eol, at cp/parser.cc:4107 5 | } | ^ 0x8e6af9 cp_parser_skip_to_pragma_eol ../../gcc/cp/parser.cc:4107 0x8e6e12 cp_parser_skip_to_end_of_statement ../../gcc/cp/parser.cc:394q3 0x8fc7b4 cp_parser_gnu_attributes_opt ../../gcc/cp/parser.cc:28676 0x92749b cp_parser_elaborated_type_specifier ../../gcc/cp/parser.cc:20341 0x908cf3 cp_parser_type_specifier ../../gcc/cp/parser.cc:19375 0x909e06 cp_parser_decl_specifier_seq ../../gcc/cp/parser.cc:15911 0x90aa81 cp_parser_simple_declaration ../../gcc/cp/parser.cc:15159 0x90c779 cp_parser_declaration_statement ../../gcc/cp/parser.cc:14367 0x90ce9b cp_parser_statement ../../gcc/cp/parser.cc:12452 0x90def4 cp_parser_statement_seq_opt ../../gcc/cp/parser.cc:12856 0x90dfd7 cp_parser_compound_statement ../../gcc/cp/parser.cc:12808 0x934560 cp_parser_function_body ../../gcc/cp/parser.cc:25062 0x934560 cp_parser_ctor_initializer_opt_and_function_body ../../gcc/cp/parser.cc:25113 0x934bda cp_parser_function_definition_after_declarator ../../gcc/cp/parser.cc:31243 0x935e64 cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/cp/parser.cc:31159 0x935e64 cp_parser_init_declarator ../../gcc/cp/parser.cc:22584 0x90abe2 cp_parser_simple_declaration ../../gcc/cp/parser.cc:15286 0x93d40e cp_parser_declaration ../../gcc/cp/parser.cc:14972 0x93df8d cp_parser_translation_unit ../../gcc/cp/parser.cc:5012 0x93df8d c_parse_file() ../../gcc/cp/parser.cc:48051
next reply other threads:[~2022-02-21 21:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-21 21:29 gscfq@t-online.de [this message] 2022-02-22 1:19 ` [Bug c++/104623] " pinskia at gcc dot gnu.org 2022-02-22 10:31 ` rguenth at gcc dot gnu.org 2022-02-22 19:23 ` mpolacek at gcc dot gnu.org 2022-02-22 19:28 ` mpolacek at gcc dot gnu.org 2022-03-11 14:07 ` jakub at gcc dot gnu.org 2022-03-15 8:15 ` cvs-commit at gcc dot gnu.org 2022-03-15 8:20 ` [Bug c++/104623] [11 " jakub at gcc dot gnu.org 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2023-05-29 10:06 ` 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-104623-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).