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/101062] New: wrong code with "-O2 -fno-toplevel-reorder -frename-registers" Date: Mon, 14 Jun 2021 11:05:42 +0000 [thread overview] Message-ID: <bug-101062-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101062 Bug ID: 101062 Summary: wrong code with "-O2 -fno-toplevel-reorder -frename-registers" 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 *, ...); union a { signed b : 5; }; int c; volatile union a d[7] = {{8}}; short e = 1; void f() { c = 5; for (; c; c--) { short *g = &e; *g = d[6].b = 0; } } int main() { f(); printf("%d\n", e); } ******************************************************************************* 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 20210613 (experimental) (GCC) git version: 681143b9b94d7f1c88a7c34e2250865c31191959 ******************************************************************************* Command Lines: $ gcc a.c -o a1.out $ gcc -O2 -fno-toplevel-reorder -frename-registers -Wall -Wextra -fno-strict-aliasing -fwrapv a.c -o a2.out $ ./a1.out 0 $ ./a2.out 1
next reply other threads:[~2021-06-14 11:05 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-14 11:05 suochenyao at 163 dot com [this message] 2021-06-14 18:04 ` [Bug tree-optimization/101062] [10/11/12 Regression] " jakub at gcc dot gnu.org 2021-06-14 18:08 ` jakub at gcc dot gnu.org 2021-06-14 18:35 ` jakub at gcc dot gnu.org 2021-06-14 18:59 ` jakub at gcc dot gnu.org 2021-06-14 20:20 ` jakub at gcc dot gnu.org 2021-06-14 21:46 ` ebotcazou at gcc dot gnu.org 2021-06-15 7:42 ` rguenth at gcc dot gnu.org 2021-06-15 8:15 ` jakub at gcc dot gnu.org 2021-06-15 8:56 ` [Bug middle-end/101062] " rguenther at suse dot de 2021-06-15 9:05 ` jakub at gcc dot gnu.org 2021-06-15 9:21 ` rguenth at gcc dot gnu.org 2021-06-16 10:18 ` cvs-commit at gcc dot gnu.org 2021-06-17 8:20 ` jakub at gcc dot gnu.org 2021-06-17 8:22 ` jakub at gcc dot gnu.org 2021-06-17 9:13 ` ebotcazou at gcc dot gnu.org 2021-06-18 9:21 ` cvs-commit at gcc dot gnu.org 2021-06-18 9:23 ` cvs-commit at gcc dot gnu.org 2021-06-18 9:23 ` cvs-commit at gcc dot gnu.org 2021-07-13 13:13 ` [Bug middle-end/101062] [10 " jakub at gcc dot gnu.org 2022-05-10 8:18 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:19 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:20 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:20 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-101062-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: linkBe 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).