public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113674] New: [[____attr____]] causes internal compiler error: in decl_attributes, at attribs.cc:776
Date: Tue, 30 Jan 2024 21:44:49 +0000	[thread overview]
Message-ID: <bug-113674-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113674

            Bug ID: 113674
           Summary: [[____attr____]] causes internal compiler error: in
                    decl_attributes, at attribs.cc:776
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mpolacek at gcc dot gnu.org
  Target Milestone: ---

[[____noreturn____]] int
g (int i)
{
  return i;
}

causes (both cc1 and cc1plus):

q.C:2:9: internal compiler error: in decl_attributes, at attribs.cc:776
    2 | g (int i)
      |         ^
0x1209fe5 decl_attributes(tree_node**, tree_node*, int, tree_node*)
        /home/mpolacek/src/gcc/gcc/attribs.cc:776
0xeed5cd cplus_decl_attributes(tree_node**, tree_node*, int)
        /home/mpolacek/src/gcc/gcc/cp/decl2.cc:1880
0xeb8604 grokfndecl
        /home/mpolacek/src/gcc/gcc/cp/decl.cc:10973
0xec6a60 grokdeclarator(cp_declarator const*, cp_decl_specifier_seq*,
decl_context, int, tree_node**)
        /home/mpolacek/src/gcc/gcc/cp/decl.cc:15063
0xed73ad start_function(cp_decl_specifier_seq*, cp_declarator const*,
tree_node*)
        /home/mpolacek/src/gcc/gcc/cp/decl.cc:18159
0x10563ef cp_parser_function_definition_from_specifiers_and_declarator
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:32573
0x1042ac8 cp_parser_init_declarator
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:23356
0x1034027 cp_parser_simple_declaration
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:15890
0x1033b9d cp_parser_block_declaration
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:15709
0x103379d cp_parser_declaration
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:15563
0x103387d cp_parser_toplevel_declaration
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:15584
0x101ac64 cp_parser_translation_unit
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:5276
0x1092a8f c_parse_file()
        /home/mpolacek/src/gcc/gcc/cp/parser.cc:51174
0x12a67d8 c_common_parse_file()
        /home/mpolacek/src/gcc/gcc/c-family/c-opts.cc:1301

             reply	other threads:[~2024-01-30 21:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 21:44 mpolacek at gcc dot gnu.org [this message]
2024-01-30 21:46 ` [Bug c++/113674] [11/12/13/14 Regression] " mpolacek at gcc dot gnu.org
2024-01-31  8:21 ` rguenth at gcc dot gnu.org
2024-01-31 16:06 ` mpolacek at gcc dot gnu.org
2024-01-31 16:38 ` jakub at gcc dot gnu.org
2024-01-31 16:54 ` mpolacek at gcc dot gnu.org
2024-01-31 18:40 ` jsm28 at gcc dot gnu.org
2024-02-12 12:23 ` jakub at gcc dot gnu.org
2024-02-12 19:45 ` cvs-commit at gcc dot gnu.org
2024-02-12 19:48 ` [Bug c++/113674] [11/12/13 " jakub at gcc dot gnu.org
2024-03-02  0:38 ` cvs-commit at gcc dot gnu.org
2024-03-04 12:08 ` [Bug c++/113674] [11/12 " jakub at gcc dot gnu.org
2024-06-11 10:37 ` cvs-commit at gcc dot gnu.org
2024-06-11 10:50 ` [Bug c++/113674] [11 " jakub at gcc dot gnu.org
2024-06-20 13:22 ` cvs-commit at gcc dot gnu.org
2024-06-20 13:38 ` 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-113674-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: link
Be 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).