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/101972] New: wrong code at -O2 on x86_64-linux-gnu
Date: Thu, 19 Aug 2021 02:51:32 +0000	[thread overview]
Message-ID: <bug-101972-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101972
           Summary: wrong code at -O2 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 regression in gcc-9. gcc-8 works fine.


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

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

$ gcc-8 -O2 abc.c ; ./a.out
30

$ cat abc.c
int a, b, c, d, f;
static short e = 63891;
char g = 30;
unsigned h(i, j) { return i << j; }
int *l(int *);
void m() {
  a = 0;
  for (; a >= 0; a--) {
    int *k = &b;
    *k = e < 0;
  }
  c = b;
  l(&c);
}
int *l(int *i) {
  d = 2;
  for (; d <= 6; d++) {
    if (h(d, *i) <= d)
      ;
    else
      continue;
    g = 0;
    return &f;
  }
}
int main() {
  m();
  printf("%d\n", g);
}

             reply	other threads:[~2021-08-19  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19  2:51 qrzhang at gatech dot edu [this message]
2021-08-19  2:52 ` [Bug tree-optimization/101972] " qrzhang at gatech dot edu
2021-08-19  2:53 ` [Bug tree-optimization/101972] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-08-19  7:33 ` marxin at gcc dot gnu.org
2021-08-19  7:59 ` rguenth at gcc dot gnu.org
2022-01-24 12:15 ` [Bug tree-optimization/101972] [9/10/11/12 Regression] wrong code at -O2 after r9-4145 cvs-commit at gcc dot gnu.org
2022-01-24 12:46 ` [Bug tree-optimization/101972] [9/10/11 " 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-101972-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).