public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110924] New: ICE on valid code at -O{s,2,3} on x86_64-linux-gnu: verify_ssa failed
Date: Sun, 06 Aug 2023 23:20:20 +0000	[thread overview]
Message-ID: <bug-110924-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110924
           Summary: ICE on valid code at -O{s,2,3} on x86_64-linux-gnu:
                    verify_ssa failed
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhendong.su at inf dot ethz.ch
  Target Milestone: ---

It appears to be a recent regression.

Compiler Explorer: https://godbolt.org/z/z9oPe5bnx

[608] % gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/local/home/suz/suz-local/software/local/gcc-trunk/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --disable-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230805 (experimental) (GCC)
[609] %
[609] % gcctk -O2 small.c
small.c: In function ‘main’:
small.c:8:5: error: stmt with wrong VUSE
    8 | int main() {
      |     ^~~~
# VUSE <.MEM_11>
e.3_2 = e;
expected .MEM_12
during GIMPLE pass: sink
small.c:8:5: internal compiler error: verify_ssa failed
0x124c54d verify_ssa(bool, bool)
        ../../gcc-trunk/gcc/tree-ssa.cc:1203
0xed05e5 execute_function_todo
        ../../gcc-trunk/gcc/passes.cc:2095
0xed0a3b execute_todo
        ../../gcc-trunk/gcc/passes.cc:2142
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
[610] %
[610] % cat small.c
int a[1], b, c, d, e, f, g;
void h(int i, int j) {
  int *k = 0;
  if (*k)
    h(0, 0);
  g = i && d;
}
int main() {
  if (c)
    goto l;
  if (!a)
    while (1) {
      f = 1;
      while (f)
        h(b && main(), e);
      while (1)
        ;
    l:;
    }
  return 0;
}

             reply	other threads:[~2023-08-06 23:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 23:20 zhendong.su at inf dot ethz.ch [this message]
2023-08-07  0:27 ` [Bug tree-optimization/110924] [14 Regression] " pinskia at gcc dot gnu.org
2023-08-07  0:31 ` pinskia at gcc dot gnu.org
2023-08-07  0:44 ` pinskia at gcc dot gnu.org
2023-08-07  7:07 ` dcb314 at hotmail dot com
2023-08-07  7:15 ` pinskia at gcc dot gnu.org
2023-08-07  7:27 ` pinskia at gcc dot gnu.org
2023-08-07  7:37 ` dcb314 at hotmail dot com
2023-08-08  7:19 ` dcb314 at hotmail dot com
2023-08-08  8:49 ` rguenth at gcc dot gnu.org
2023-08-08  9:36 ` rguenth at gcc dot gnu.org
2023-08-08  9:38 ` rguenth at gcc dot gnu.org
2023-08-08  9:42 ` rguenth at gcc dot gnu.org
2023-08-08 10:26 ` rguenth at gcc dot gnu.org
2023-08-08 12:24 ` cvs-commit at gcc dot gnu.org
2023-08-08 12:24 ` 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-110924-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).