public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101445] New: wrong code at -O3 on x86_64-linux-gnu
Date: Wed, 14 Jul 2021 02:50:09 +0000	[thread overview]
Message-ID: <bug-101445-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101445
           Summary: wrong code at -O3 on x86_64-linux-gnu
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: qrzhang at gatech dot edu
  Target Milestone: ---

It appears to be a recent regression. Note that -O2 works fine.

$ gcc-trunk -v
Supported LTO compression algorithms: zlib
gcc version 12.0.0 20210713 (experimental) [master revision
7670b6633e5:d2f95d2ac56:1583b8bff0be7e41aa721dde79f90ca0763bd4e2] (GCC)


$ gcc-trunk abc.c ; ./a.out
0
0
0
0
0
0
0



$ gcc-trunk -O3 abc.c ; ./a.out
0
0
3
0
0
0
0



$ cat abc.c
int a[35] = {1, 1, 3};
char b = 4;
int c, d;
int main() {
  char e;
  for (; b >= 0; b--) {
    e = 3;
    for (; e >= 0; e--)
      a[b * 5 + e] = a[b * 5 + e + 1];
  }
  for (; c < 5; c++)
    ;
  for (; d < 7; d++)
    printf("%d\n", a[c * d]);
}

             reply	other threads:[~2021-07-14  2:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14  2:50 qrzhang at gatech dot edu [this message]
2021-07-14  2:50 ` [Bug tree-optimization/101445] " qrzhang at gatech dot edu
2021-07-14  2:58 ` [Bug tree-optimization/101445] [11/12 Regression] " pinskia at gcc dot gnu.org
2021-07-14  6:12 ` rguenth at gcc dot gnu.org
2021-07-14  8:58 ` rguenth at gcc dot gnu.org
2021-07-14 10:31 ` cvs-commit at gcc dot gnu.org
2021-07-14 11:09 ` cvs-commit at gcc dot gnu.org
2021-07-14 11:09 ` 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-101445-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).