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/101885] New: wrong code at -O3 on x86_64-linux-gnu
Date: Thu, 12 Aug 2021 17:09:49 +0000	[thread overview]
Message-ID: <bug-101885-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101885
           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 a regression in gcc-10. gcc-9 works fine.


$ gcc-trunk -v
gcc version 12.0.0 20210812 (experimental) [master revision
01f8a8b48e5:0eb7800d242:04b4f3152593f85b05974528d1607619dd77d702] (GCC)


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

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


$ cat abc.c
int a = 3, c;
short b = 5, d, f;
volatile short e;
int main() {
  f = 29;
  for (; f != 33; f++) {
    int g = a;
    if (b)
      if (a) {
        a = b = 0;
        for (; b <= 8; b++)
          ;
      }
    e;
    e;
    c = 0;
    for (; c != 14; ++c)
      e;
  }
  b = d;
  printf("", 8);
  printf("%d\n", a);
}

             reply	other threads:[~2021-08-12 17:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 17:09 qrzhang at gatech dot edu [this message]
2021-08-12 17:10 ` [Bug tree-optimization/101885] " qrzhang at gatech dot edu
2021-08-12 21:06 ` [Bug rtl-optimization/101885] [10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-08-12 21:22 ` pinskia at gcc dot gnu.org
2021-08-12 21:23 ` pinskia at gcc dot gnu.org
2021-08-16  7:34 ` rguenth at gcc dot gnu.org
2022-01-20 15:29 ` jakub at gcc dot gnu.org
2022-01-20 15:40 ` jakub at gcc dot gnu.org
2022-01-20 16:55 ` jakub at gcc dot gnu.org
2022-01-20 17:15 ` jakub at gcc dot gnu.org
2022-01-20 17:27 ` jakub at gcc dot gnu.org
2022-01-20 17:29 ` jakub at gcc dot gnu.org
2022-01-20 18:00 ` jakub at gcc dot gnu.org
2022-02-03 11:07 ` roger at nextmovesoftware dot com
2022-02-04  1:03 ` segher at gcc dot gnu.org
2022-02-04  9:38 ` cvs-commit at gcc dot gnu.org
2022-02-10 22:26 ` [Bug rtl-optimization/101885] [10/11 " roger at nextmovesoftware dot com
2022-03-16  7:37 ` roger at nextmovesoftware dot com
2022-03-16  8:10 ` rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2023-07-07 10:40 ` [Bug rtl-optimization/101885] [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-101885-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).