public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101009] [10/11/12 Regression] wrong code with "-O3 -fno-tree-sra" Date: Fri, 11 Jun 2021 07:21:44 +0000 [thread overview] Message-ID: <bug-101009-4-Ku6b3adA34@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101009 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[12 Regression] wrong code |[10/11/12 Regression] wrong |with "-O3 -fno-tree-sra" |code with "-O3 | |-fno-tree-sra" Target Milestone|12.0 |10.4 Known to work| |9.4.0 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- With -O2 -fno-tree-sra -fno-tree-pre -ftree-loop-distribution even GCC 10 miscompiles the code. For dg-torture: /* { dg-do run } */ /* { dg-additional-options "-fno-tree-sra -fno-tree-pre -ftree-loop-distribution" } */ 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]; } if (e.c != 1) __builtin_abort (); return 0; }
next prev parent reply other threads:[~2021-06-11 7:21 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 8:17 [Bug tree-optimization/101009] New: " suochenyao at 163 dot com 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 ` rguenth at gcc dot gnu.org [this message] 2021-06-11 7:33 ` [Bug tree-optimization/101009] [10/11/12 " 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-Ku6b3adA34@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).