public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65533] [5 Regression] 252.eon in SPEC CPU 2000 failed to build Date: Tue, 24 Mar 2015 07:54:00 -0000 [thread overview] Message-ID: <bug-65533-4-iQPII1qolU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65533-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65533 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- C testcase: struct A { int a[2]; }; struct B { double b[2]; }; struct C { double c[4][1]; }; static void inline bar (struct B *x, double y, double z) { x->b[0] = y; x->b[1] = z; } void baz (struct B *); void foo (struct C *x, struct A *y) { struct B d; bar (&d, x->c[1][0] * y->a[0] + x->c[0][1] * y->a[1] + x->c[0][0] * x->c[0][1], x->c[0][0] * y->a[0] + x->c[0][1] * y->a[1] + x->c[0][1] * y->a[0] + x->c[0][0]); baz (&d); }
next prev parent reply other threads:[~2015-03-24 7:21 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-24 2:19 [Bug middle-end/65533] New: " hjl.tools at gmail dot com 2015-03-24 7:09 ` [Bug middle-end/65533] " hjl.tools at gmail dot com 2015-03-24 7:54 ` jakub at gcc dot gnu.org [this message] 2015-03-24 8:00 ` jakub at gcc dot gnu.org 2015-03-24 8:43 ` [Bug tree-optimization/65533] " jakub at gcc dot gnu.org 2015-03-24 8:49 ` jakub at gcc dot gnu.org 2015-03-24 9:10 ` rguenth at gcc dot gnu.org 2015-03-24 9:16 ` rguenth at gcc dot gnu.org 2015-03-24 9:32 ` rguenther at suse dot de 2015-03-24 10:53 ` jakub at gcc dot gnu.org 2015-03-24 11:43 ` 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-65533-4-iQPII1qolU@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).