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/65832] Inefficient vector construction Date: Tue, 28 Apr 2015 08:55:00 -0000 [thread overview] Message-ID: <bug-65832-4-csqi7r7RxE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65832 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uros at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Somehow we get into very weird initial RTL generated by expand... (insn 12 11 13 (set (reg:V2DI 101) (mult:V2DI (zero_extend:V2DI (vec_select:V2SI (reg:V4SI 95 [ vect_cst_.7 ]) (parallel [ (const_int 0 [0]) (const_int 2 [0x2]) ]))) (zero_extend:V2DI (vec_select:V2SI (mem/c:V4SI (reg/f:DI 94) [1 MEM[(unsigned int *)&in]+0 S16 A256]) (parallel [ (const_int 0 [0]) (const_int 2 [0x2]) ]))))) t.c:17 -1 (nil)) (WTF!? As if there were no integer vector multiply with SSE2 but only DImode ones?!)
next prev parent reply other threads:[~2015-04-28 8:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-21 13:56 [Bug target/65832] New: " rguenth at gcc dot gnu.org 2015-04-21 14:03 ` [Bug target/65832] " rguenth at gcc dot gnu.org 2015-04-21 14:11 ` rguenth at gcc dot gnu.org 2015-04-28 8:51 ` rguenth at gcc dot gnu.org 2015-04-28 8:55 ` rguenth at gcc dot gnu.org [this message] 2015-05-22 12:15 ` rguenth at gcc dot gnu.org 2015-06-01 10:30 ` rguenth at gcc dot gnu.org 2020-06-24 20:45 ` [Bug middle-end/65832] " gabravier at gmail dot com
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-65832-4-csqi7r7RxE@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).