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/105636] New: ICE in gen_ctf_array_type, at dwarf2ctf.cc:379
Date: Tue, 17 May 2022 18:49:28 +0000	[thread overview]
Message-ID: <bug-105636-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105636
           Summary: ICE in gen_ctf_array_type, at dwarf2ctf.cc:379
           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: ---

With file ./gcc/testsuite/gcc.dg/gnu99-const-expr-4.c
and option -gctf or -gbtf, at -O0 :


$ gcc-13-20220515 -c gnu99-const-expr-4.c -gctf
gnu99-const-expr-4.c:29:1: internal compiler error: in gen_ctf_array_type, at
dwarf2ctf.cc:379
   29 | static int (*a7)[] = (__typeof__((int (*)[n])sa + m++))sa; /* {
dg-error "constant" } */
      | ^~~~~~
0x852783 gen_ctf_array_type
        ../../gcc/dwarf2ctf.cc:379
0x852783 gen_ctf_type
        ../../gcc/dwarf2ctf.cc:881
0x852ddd ctf_do_die(die_struct*)
        ../../gcc/dwarf2ctf.cc:973
0x85691b ctf_debug_do_cu
        ../../gcc/dwarf2out.cc:32877
0x8a2461 dwarf2out_early_finish
        ../../gcc/dwarf2out.cc:33006
0x80cbff symbol_table::finalize_compilation_unit()
        ../../gcc/cgraphunit.cc:2525

             reply	other threads:[~2022-05-17 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 18:49 gscfq@t-online.de [this message]
2022-05-18  7:39 ` [Bug debug/105636] -gctf causes an ICE on some invalid code marxin at gcc dot gnu.org
2022-05-19 19:15 ` ibhagat at gcc dot gnu.org
2022-05-19 21:31 ` ibhagat 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-105636-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).