public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55755] New: Invalid VIEW_CONVERT_EXPR produced by SRA Date: Thu, 20 Dec 2012 14:22:00 -0000 [thread overview] Message-ID: <bug-55755-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55755 Bug #: 55755 Summary: Invalid VIEW_CONVERT_EXPR produced by SRA Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: jamborm@gcc.gnu.org Sigh. Even after all those years I can still occasionally come up with an ICEing SRA testcase (it's basically a slightly modified /home/mjambor/gcc/mine/src/gcc/testsuite/gcc.dg/torture/pr47228.c). To be run with -O only, fails on x86_64-linux trunk, 4.7, and 4.6 (when checking is enabled): /* { dg-do run } */ /* { dg-require-effective-target int32plus } */ struct S4 { unsigned f0:24; } __attribute__((__packed__)); struct S4 g_10 = { 6210831 }; struct S5 { int i; struct S4 l_8[2]; } __attribute__((__packed__)); int a, b; struct S4 func_2 (int x) { struct S5 l = { 0, {{0}, {0}} }; l.i = a; g_10 = l.l_8[1]; for (; x<2; x++) { struct S4 tmp = { 11936567 }; l.l_8[x] = tmp; } b = l.i; return g_10; } int main (void) { func_2 (0); return 0; }
next reply other threads:[~2012-12-20 14:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-20 14:22 jamborm at gcc dot gnu.org [this message] 2012-12-20 14:28 ` [Bug tree-optimization/55755] " jamborm at gcc dot gnu.org 2013-01-04 13:03 ` jamborm at gcc dot gnu.org 2013-01-04 13:21 ` jamborm at gcc dot gnu.org 2013-01-24 14:54 ` jamborm at gcc dot gnu.org 2013-01-24 15:41 ` jamborm at gcc dot gnu.org 2013-01-24 15:53 ` jamborm 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-55755-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).