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/102149] New: wrong code at -O3 on x86_64-linux-gnu
Date: Tue, 31 Aug 2021 19:38:25 +0000	[thread overview]
Message-ID: <bug-102149-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102149
           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: ---

Seems to be a recent regression.


$ gcc-trunk -v
gcc version 12.0.0 20210831 (experimental) [master revision
5e57bacf6f3:a82c79a304b:de7a795c321e76826d123c92b99e73e144666b60] (GCC)


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

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

$ cat abc.c
int a[8];
int *b = &a[6];
char c;
int main() {
  int d = 7;
  for (; d >= 0; d--) {
    *b = 1;
    c = a[d] >> 3;
    a[d] = c;
  }
  printf("%d\n", a[6]);
}

             reply	other threads:[~2021-08-31 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 19:38 qrzhang at gatech dot edu [this message]
2021-08-31 19:40 ` [Bug tree-optimization/102149] " qrzhang at gatech dot edu
2021-08-31 19:44 ` jakub at gcc dot gnu.org
2021-08-31 20:17 ` pinskia at gcc dot gnu.org
2021-09-01  6:05 ` rguenth at gcc dot gnu.org
2021-09-01  7:51 ` cvs-commit at gcc dot gnu.org
2021-09-01  7:51 ` 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-102149-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).