public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/36445] New: [4.4 Regression] ICE in expand_expr_real_1 with -O1 with vector registers Date: Thu, 05 Jun 2008 21:41:00 -0000 [thread overview] Message-ID: <bug-36445-6528@http.gcc.gnu.org/bugzilla/> (raw) Another fallout due to the using VCE more patch: #define vector __attribute__((vector_size(16) )) struct struct1 { union { float a[3]; } vmx; struct struct2 { struct2(const struct2& r) {} } w; } __attribute__((aligned(16))); struct struct3 { vector float vmx; operator const struct1& () const{ return *reinterpret_cast<const struct1*>(this); } }; struct3 func3( struct3 V1); struct3 func2( void ); void func1( ) { struct1 vVec = func2() ; func3 ( (struct3&)vVec ); } --- CUT --- This time you need to compile with -O2 -maltivec and it does not happen under x86 for some reason. -- Summary: [4.4 Regression] ICE in expand_expr_real_1 with -O1 with vector registers Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org GCC target triplet: powerpc*-*-* http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36445
next reply other threads:[~2008-06-05 21:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-06-05 21:41 pinskia at gcc dot gnu dot org [this message] 2008-06-05 21:41 ` [Bug middle-end/36445] " pinskia at gcc dot gnu dot org 2008-06-25 12:10 ` rguenth at gcc dot gnu dot org 2008-06-30 0:30 ` pinskia at gcc dot gnu dot org 2008-08-31 2:44 ` pinskia at gcc dot gnu dot org 2008-09-03 19:29 ` pinskia at gcc dot gnu dot org 2008-09-03 19:30 ` pinskia at gcc dot gnu dot 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-36445-6528@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).