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 target/51996] ICE in extract_insn gcc.dg/pr48335-5.c Date: Wed, 25 Jan 2012 12:48:00 -0000 [thread overview] Message-ID: <bug-51996-4-c5dU7WayWM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51996-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51996 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-01-25 CC|rguenther at suse dot de |rguenth at gcc dot gnu.org Component|regression |target Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-25 12:29:49 UTC --- Looks like a target bug to me, needs -O -mfpu=neon -mfloat-abi=softfp to trigger. typedef long long T __attribute__((may_alias)); struct S { _Complex float d __attribute__((aligned (8))); }; int f1 (struct S x) { struct S s = x; return *(T *) &s.d; } expands from f1 (struct S x) { T D.4964; int D.4957; <bb 2>: D.4964_1 = VIEW_CONVERT_EXPR<T>(x); D.4957_3 = (int) D.4964_1; return D.4957_3; } and the target emits (insn 9 0 0 (set (reg:DI 140) (unspec:DI [ (mem/s/c:DI (plus:SI (reg/f:SI 129 virtual-stack-vars) (const_int -8 [0xfffffffffffffff8])) [0 S8 A32]) ] UNSPEC_MISALIGNED_ACCESS)) t.c:11 -1 (nil)) for a DImode movmisalign of (mem/s/c:SC (plus:SI (reg/f:SI 129 virtual-stack-vars) (const_int -8 [0xfffffffffffffff8])) [0 S8 A32])
prev parent reply other threads:[~2012-01-25 12:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 12:41 [Bug regression/51996] New: " Greta.Yorsh at arm dot com 2012-01-25 12:48 ` rguenth at gcc dot gnu.org [this message]
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-51996-4-c5dU7WayWM@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).