public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "suochenyao at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101009] New: wrong code with "-O3 -fno-tree-sra"
Date: Thu, 10 Jun 2021 08:17:34 +0000	[thread overview]
Message-ID: <bug-101009-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101009
           Summary: wrong code with "-O3 -fno-tree-sra"
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: suochenyao at 163 dot com
  Target Milestone: ---

*******************************************************************************
OS and Platform:
CentOS Linux release 7.8.2003 (Core), x86_64 GNU/Linux
*******************************************************************************
Program:
int printf(const char *, ...);
struct a {
  unsigned b;
  unsigned c;
} e, *f = &e;
int d = 1;
int main() {
  for (; d; d--) {
    struct a g[] = {{2, 1}, {2, 1}};
    *f = g[1];
  }
  printf("%d\n", e.c);
}
*******************************************************************************
gcc version:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/data/bin/gcc-dev/bin/gcc
COLLECT_LTO_WRAPPER=/data/bin/gcc-dev/libexec/gcc/x86_64-pc-linux-gnu/12.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../configure --prefix=/data/bin/gcc-dev --disable-multilib
--enable-languages=c,c++
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.0.0 20210609 (experimental) (GCC)

git version: 53cb324cb4f9475d4eabcd9f5a858c5edaacc0cf
*******************************************************************************
Command Lines:
$ gcc -O3 -fno-tree-sra -Wall -Wextra -fno-strict-aliasing -fwrapv a.c -o
a1.out
$ gcc a.c -o a2.out
$ ./a1.out
0
$ ./a2.out
1

             reply	other threads:[~2021-06-10  8:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  8:17 suochenyao at 163 dot com [this message]
2021-06-10  9:28 ` [Bug tree-optimization/101009] [12 Regression] " rguenth at gcc dot gnu.org
2021-06-10  9:40 ` rguenth at gcc dot gnu.org
2021-06-10 13:38 ` jakub at gcc dot gnu.org
2021-06-11  6:08 ` rguenth at gcc dot gnu.org
2021-06-11  6:23 ` rguenth at gcc dot gnu.org
2021-06-11  6:41 ` rguenth at gcc dot gnu.org
2021-06-11  7:19 ` rguenth at gcc dot gnu.org
2021-06-11  7:21 ` [Bug tree-optimization/101009] [10/11/12 " rguenth at gcc dot gnu.org
2021-06-11  7:33 ` rguenth at gcc dot gnu.org
2021-06-11  9:15 ` jakub at gcc dot gnu.org
2021-06-11  9:26 ` cvs-commit at gcc dot gnu.org
2021-06-11  9:27 ` [Bug tree-optimization/101009] [10/11 " rguenth at gcc dot gnu.org
2021-06-16 13:12 ` cvs-commit at gcc dot gnu.org
2021-09-06 10:18 ` [Bug tree-optimization/101009] [10 " cvs-commit at gcc dot gnu.org
2021-09-06 10:18 ` 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-101009-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).