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/107683] New: [13 Regression] ICE in int_fits_type_p, at tree.cc:8044
Date: Mon, 14 Nov 2022 17:32:01 +0000	[thread overview]
Message-ID: <bug-107683-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107683
           Summary: [13 Regression] ICE in int_fits_type_p, at
                    tree.cc:8044
           Product: gcc
           Version: 13.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 20221023 and 20221030 :
(gcc configured with --enable-checking=yes)


$ cat z1.c
enum e : int
enum e { E };


$ gcc-13-20221106 -c z1.c
z1.c:2:6: error: 'enum' declared with but defined without fixed underlying type
    2 | enum e { E };
      |      ^
z1.c:2:10: internal compiler error: Segmentation fault
    2 | enum e { E };
      |          ^
0xeeafcf crash_signal
        ../../gcc/toplev.cc:314
0x1246f30 int_fits_type_p(tree_node const*, tree_node const*)
        ../../gcc/tree.cc:8044
0x7c4d8b build_enumerator(unsigned int, unsigned int, c_enum_contents*,
tree_node*, tree_node*)
        ../../gcc/c/c-decl.cc:9786
0x82c01f c_parser_enum_specifier
        ../../gcc/c/c-parser.cc:3469
0x82c01f c_parser_declspecs(c_parser*, c_declspecs*, bool, bool, bool, bool,
bool, bool, bool, c_lookahead_kind)
        ../../gcc/c/c-parser.cc:3150
0x82cc91 c_parser_enum_specifier
        ../../gcc/c/c-parser.cc:3367
0x82cc91 c_parser_declspecs(c_parser*, c_declspecs*, bool, bool, bool, bool,
bool, bool, bool, c_lookahead_kind)
        ../../gcc/c/c-parser.cc:3150
0x850305 c_parser_declaration_or_fndef
        ../../gcc/c/c-parser.cc:2091
0x85cf8f c_parser_external_declaration
        ../../gcc/c/c-parser.cc:1833
0x85d8bd c_parser_translation_unit
        ../../gcc/c/c-parser.cc:1695
0x85d8bd c_parse_file()
        ../../gcc/c/c-parser.cc:24359
0x8da031 c_common_parse_file()
        ../../gcc/c-family/c-opts.cc:1244

             reply	other threads:[~2022-11-14 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 17:32 gscfq@t-online.de [this message]
2022-11-14 19:34 ` [Bug c/107683] " mpolacek at gcc dot gnu.org
2022-11-16 12:43 ` rguenth at gcc dot gnu.org
2023-04-26  6:57 ` [Bug c/107683] [13/14 " rguenth at gcc dot gnu.org
2023-07-27  9:24 ` rguenth at gcc dot gnu.org
2024-03-23 21:39 ` pinskia at gcc dot gnu.org
2024-03-23 21:44 ` pinskia 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-107683-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).