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/95045] New: wrong code at -O3 on x86_64-linux-gnu Date: Mon, 11 May 2020 05:11:07 +0000 [thread overview] Message-ID: <bug-95045-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95045 Bug ID: 95045 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: --- Recent regression. Bisection points to g:283cb9ea6293e813e4 $ gcc-trunk -v gcc version 11.0.0 20200510 (experimental) [master revision 4ae915cdbf0:8eedda9eef3:ef6394205d7bcab00dca01182d708ad5a6360a7b] (GCC) $ gcc-trunk abc.c ; ./a.out 4 $ gcc-trunk -O3 abc.c ; ./a.out 0 $ cat abc.c int a, c, f; long b; char d; int e[3]; int g[9][3][2]; int main() { { h: for (f = 0; f <= 5; f++) { b = 3; for (; b >= 0; b--) { e[2] = d = 0; for (; d <= 3; d++) { g[8][2][0] = e[1] = c = 0; for (; c <= 1; c++) e[c + 1] = g[d + 5][2][c] = 4; } if (a) goto h; } } } printf("%d\n", e[2]); }
next reply other threads:[~2020-05-11 5:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 5:11 qrzhang at gatech dot edu [this message] 2020-05-11 6:55 ` [Bug tree-optimization/95045] " rguenth at gcc dot gnu.org 2020-05-11 7:27 ` [Bug tree-optimization/95045] [11 Regression] " marxin at gcc dot gnu.org 2020-05-11 8:01 ` rguenth at gcc dot gnu.org 2020-05-12 6:22 ` cvs-commit at gcc dot gnu.org 2020-05-12 6:26 ` 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-95045-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).