public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96467] New: [8/9/10/11 Regression] in finish_member_declaration, at cp/semantics.c:3240
Date: Tue, 04 Aug 2020 16:29:35 +0000	[thread overview]
Message-ID: <bug-96467-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 96467
           Summary: [8/9/10/11 Regression] in finish_member_declaration,
                    at cp/semantics.c:3240
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: haoxintu at gmail dot com
  Target Milestone: ---

Hi, all.

This code makes GCC-9.1 onwards versions ICE without any error messages. I
guess this case is more seriously because this makes released versions ICE
rather than "confused by earlier errors".

Input:
//small.cc
union a;
a :: b () alignas (enum {c});

Command:
g++ small.cc

Output:
small.cc:2:26: internal compiler error: in finish_member_declaration, at
cp/semantics.c:3240
    2 | a :: b () alignas (enum {c});
      |                          ^
0x5c82c0 finish_member_declaration(tree_node*)
        ../../gcc/cp/semantics.c:3240
0x67d578 build_enumerator(tree_node*, tree_node*, tree_node*, tree_node*,
unsigned int)
        ../../gcc/cp/decl.c:15887
0x6e8b47 cp_parser_enumerator_definition
        ../../gcc/cp/parser.c:19493
0x6e8b47 cp_parser_enumerator_list
        ../../gcc/cp/parser.c:19422
0x6e8b47 cp_parser_enum_specifier
        ../../gcc/cp/parser.c:19353
0x6e8b47 cp_parser_type_specifier
        ../../gcc/cp/parser.c:17683
0x6fb6f9 cp_parser_type_specifier_seq
        ../../gcc/cp/parser.c:22386
0x6f5c84 cp_parser_type_id_1
        ../../gcc/cp/parser.c:22203
0x6f5ecf cp_parser_type_id
        ../../gcc/cp/parser.c:22282
0x6f5ecf cp_parser_std_attribute_spec
        ../../gcc/cp/parser.c:27079
0x6f5ecf cp_parser_std_attribute_spec_seq
        ../../gcc/cp/parser.c:27142
0x6f3b43 cp_parser_direct_declarator
        ../../gcc/cp/parser.c:21234
0x6f3b43 cp_parser_declarator
        ../../gcc/cp/parser.c:21057
0x706577 cp_parser_init_declarator
        ../../gcc/cp/parser.c:20557
0x6e9c32 cp_parser_simple_declaration
        ../../gcc/cp/parser.c:13734
0x70f952 cp_parser_declaration
        ../../gcc/cp/parser.c:13433
0x710074 cp_parser_translation_unit
        ../../gcc/cp/parser.c:4734
0x710074 c_parse_file()
        ../../gcc/cp/parser.c:43975
0x7d84fb c_common_parse_file()
        ../../gcc/c-family/c-opts.c:1190
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

My GCC version is
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/home/haoxin/corpus-compilers/gcc-trunk/gcc-master/build/libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure
--prefix=/home/haoxin/corpus-compilers/gcc-trunk/gcc-master/build/
--enable-languages=c,c++ CC=gcc CXX=g++
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.0.0 20200801 (experimental) (GCC) 

Thanks,
Haoxin

             reply	other threads:[~2020-08-04 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04 16:29 haoxintu at gmail dot com [this message]
2020-08-04 16:34 ` [Bug c++/96467] " mpolacek at gcc dot gnu.org
2021-06-01  8:18 ` [Bug c++/96467] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:43 ` [Bug c++/96467] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-07-07 10:37 ` [Bug c++/96467] [11/12/13/14 " rguenth 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-96467-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).