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/49067] [4.5 Regression] Internal Compiler Error with -O3 Date: Fri, 20 May 2011 10:35:00 -0000 [thread overview] Message-ID: <bug-49067-4-C7IW3kPRUi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49067-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49067 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2011.05.20 10:18:43 Component|c |tree-optimization Version|4.5.2 |4.5.3 AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org |gnu.org | Target Milestone|--- |4.5.4 Summary|Internal Compiler Error |[4.5 Regression] Internal |with -O3 |Compiler Error with -O3 Ever Confirmed|0 |1 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-20 10:18:43 UTC --- static inline int armature_circle_doSelectJoint(void *userData) { struct { void *vc; short select; int mval[2]; float radius; } *data = userData; return (0 <= data->radius && data->select); } int armature_circle_select(void) { struct { void *vc; short select, mval[2]; float radius; } data; return armature_circle_doSelectJoint(&data); } it's caused by the mismatch of the local struct declarations (might be a bug in your app as well).
next prev parent reply other threads:[~2011-05-20 10:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-19 17:38 [Bug c/49067] New: " asalina at snet dot net 2011-05-20 10:21 ` [Bug c/49067] " rguenth at gcc dot gnu.org 2011-05-20 10:35 ` rguenth at gcc dot gnu.org [this message] 2011-05-20 18:48 ` [Bug c/49067] [4.5 Regression] " asalina at snet dot net 2011-08-01 14:00 ` [Bug tree-optimization/49067] " rguenth at gcc dot gnu.org 2012-07-02 10:44 ` 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-49067-4-C7IW3kPRUi@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).