public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102269] New: [12 Regression] ICE in verify_gimple_stmt since r12-3433-ga25e0b5e6ac8a77a
Date: Fri, 10 Sep 2021 07:58:37 +0000	[thread overview]
Message-ID: <bug-102269-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102269
           Summary: [12 Regression] ICE in verify_gimple_stmt since
                    r12-3433-ga25e0b5e6ac8a77a
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: qing.zhao at oracle dot com
  Target Milestone: ---

The following crashes:

$ cat auto-var.c
void fn() { int a[0]; }

$ gcc auto-var.c -c -ftrivial-auto-var-init=zero -fdump-tree-all
auto-var.c: In function ‘fn’:
auto-var.c:1:6: internal compiler error: Segmentation fault
    1 | void fn() { int a[0]; }
      |      ^~
0x14615f8 crash_signal
        /home/marxin/Programming/gcc/gcc/toplev.c:328
0x7ffff786239f ???
        ../sysdeps/unix/sysv/linux/sigaction.c:10
0x14c1ffc verify_gimple_call
        /home/marxin/Programming/gcc/gcc/tree-cfg.c:3466
0x14c8d13 verify_gimple_stmt
        /home/marxin/Programming/gcc/gcc/tree-cfg.c:5032
0x14c92f4 verify_gimple_in_seq_2
        /home/marxin/Programming/gcc/gcc/tree-cfg.c:5188
0x14c91e3 verify_gimple_in_seq_2
        /home/marxin/Programming/gcc/gcc/tree-cfg.c:5161
0x14c941c verify_gimple_in_seq(gimple*)
        /home/marxin/Programming/gcc/gcc/tree-cfg.c:5227
0x1028655 gimplify_body(tree_node*, bool)
        /home/marxin/Programming/gcc/gcc/gimplify.c:15746
0x1028922 gimplify_function_tree(tree_node*)
        /home/marxin/Programming/gcc/gcc/gimplify.c:15817
0xd543d0 cgraph_node::analyze()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:670
0xd5671d analyze_functions
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:1234
0xd59e59 symbol_table::finalize_compilation_unit()
        /home/marxin/Programming/gcc/gcc/cgraphunit.c:2508
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.

             reply	other threads:[~2021-09-10  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  7:58 marxin at gcc dot gnu.org [this message]
2021-09-10  7:58 ` [Bug tree-optimization/102269] " marxin at gcc dot gnu.org
2021-09-10  8:17 ` rguenth at gcc dot gnu.org
2021-09-10  8:53 ` [Bug tree-optimization/102269] ICE in verify_gimple_stmt and -ftrivial-auto-var-init=zero and zero size array pinskia at gcc dot gnu.org
2021-09-10  9:11 ` cvs-commit at gcc dot gnu.org
2021-09-10  9:12 ` rguenth at gcc dot gnu.org
2021-09-10  9:55 ` marxin at gcc dot gnu.org
2021-09-10 14:31 ` qinzhao at gcc dot gnu.org
2021-09-11  6:41 ` 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-102269-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).