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/114787] New: wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)
Date: Sat, 20 Apr 2024 10:53:07 +0000	[thread overview]
Message-ID: <bug-114787-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114787
           Summary: wrong code at -O1 on x86_64-linux-gnu (the generated
                    code hangs)
           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 and does not reproduce with 13.2 and
earlier. 

Compiler Explorer: https://godbolt.org/z/6sbh8Wr1e


[663] % gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/14.0.1/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.1 20240420 (experimental) (GCC) 
[664] % 
[664] % gcctk -O0 small.c; ./a.out
[665] % 
[665] % gcctk -O1 small.c
[666] % timeout -s 9 10 ./a.out
Killed
[667] % 
[667] % cat small.c
int a, b, c, d, e = -1, f, g, h, j, k, n, o, p;
int main() {
  int i, l = 2, m;
  for (b = 0; b < 1; b++)
    l = 0;
  for (; a >= 0; a--)
    for (m = 3; m; m--) {
      k = g;
      i = 0;
      for (; i < 1; i++)
        for (; f < 1; f++)
          h = g;
      n = 2 & ((e ^ d) | 1) * j;
      o = ~(e & n);
    q:
      if (c <= e)
        return 0;
      e = o;
    }
  p = l;
  l = 0;
  if (p)
    goto q;
  return 0;
}

             reply	other threads:[~2024-04-20 10:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20 10:53 zhendong.su at inf dot ethz.ch [this message]
2024-04-20 10:59 ` [Bug tree-optimization/114787] [14 Regression] " jakub at gcc dot gnu.org
2024-04-20 14:22 ` law at gcc dot gnu.org
2024-04-20 22:03 ` [Bug target/114787] " pinskia at gcc dot gnu.org
2024-04-20 23:03 ` [Bug tree-optimization/114787] " pinskia at gcc dot gnu.org
2024-04-20 23:10 ` [Bug tree-optimization/114787] [13/14 " pinskia at gcc dot gnu.org
2024-04-20 23:37 ` pinskia at gcc dot gnu.org
2024-04-20 23:50 ` pinskia at gcc dot gnu.org
2024-04-22  7:39 ` jakub at gcc dot gnu.org
2024-04-22  7:49 ` jakub at gcc dot gnu.org
2024-04-22  8:08 ` jakub at gcc dot gnu.org
2024-04-22  8:24 ` pinskia at gcc dot gnu.org
2024-04-22  9:09 ` jakub at gcc dot gnu.org
2024-04-22 12:45 ` jakub at gcc dot gnu.org
2024-04-22 13:01 ` hubicka at gcc dot gnu.org
2024-04-24  6:12 ` rguenth at gcc dot gnu.org
2024-04-24  6:47 ` rguenth at gcc dot gnu.org
2024-04-24  8:13 ` cvs-commit at gcc dot gnu.org
2024-04-24  8:14 ` [Bug tree-optimization/114787] [13 " rguenth at gcc dot gnu.org
2024-04-24 14:38 ` hubicka at gcc dot gnu.org
2024-05-06 13:15 ` cvs-commit at gcc dot gnu.org
2024-05-06 13:15 ` 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-114787-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).