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/101025] New: wrong code at -O3 on x86_64-linux-gnu Date: Fri, 11 Jun 2021 04:51:28 +0000 [thread overview] Message-ID: <bug-101025-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101025 Bug ID: 101025 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 to be a recent regression. Bisection points to g:128f43cf679e51564202b41f23fae4146347f93d $ gcc-trunk -v Supported LTO compression algorithms: zlib gcc version 12.0.0 20210610 (experimental) [master revision 5ad76ad7f5b:c64ab1c4fe0:cce1697e6fe0134616ebc8f7040d99e66c12241a] (GCC) $ gcc-trunk abc.c ; ./a.out 0 $ gcc-trunk -O3 abc.c ; ./a.out 4 $ cat abc.c int a[10]; int b, d, g; volatile char c; short e; volatile int f; int main() { for (; d <= 9; d++) { b = e = 0; for (; e < 10; e++) a[e] = 4; for (; b <= 9; b++) if (g) f = 0; else a[b] = c; } printf("%d\n", a[1]); }
next reply other threads:[~2021-06-11 4:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-11 4:51 qrzhang at gatech dot edu [this message] 2021-06-11 8:15 ` [Bug tree-optimization/101025] [11/12 Regression] " rguenth at gcc dot gnu.org 2021-06-11 8:27 ` rguenth at gcc dot gnu.org 2021-06-11 8:59 ` marxin at gcc dot gnu.org 2021-06-11 9:08 ` marxin at gcc dot gnu.org 2021-06-11 9:08 ` rguenth at gcc dot gnu.org 2021-06-11 16:13 ` cvs-commit at gcc dot gnu.org 2021-06-11 16:13 ` [Bug tree-optimization/101025] [11 " rguenth at gcc dot gnu.org 2021-06-11 16:26 ` qrzhang at gatech dot edu 2021-06-16 10:16 ` rguenth at gcc dot gnu.org 2021-07-07 14:06 ` cvs-commit at gcc dot gnu.org 2021-07-07 14:08 ` 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-101025-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).