public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52607] v4df __builtin_shuffle with {0,2,1,3} or {1,3,0,2}
Date: Wed, 11 Apr 2012 16:49:00 -0000	[thread overview]
Message-ID: <bug-52607-4-IVfofwiJqH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52607-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52607

--- Comment #28 from Marc Glisse <marc.glisse at normalesup dot org> 2012-04-11 16:48:47 UTC ---
A difficulty I hadn't foreseen is that the code that canonicalizes permutations
(and in particular checks if one of the operands is unused) is in
ix86_expand_vec_perm_const. So if I ask expand_vec_perm_1 to generate the
2-operand 0,1,2,3 permutation, it will happily generate vperm2f128 with
immediate 16 without noticing that it is the identity on the first operand. I
should probably move that code into its own function so I can call it before
expand_vec_perm_1.


  parent reply	other threads:[~2012-04-11 16:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  1:06 [Bug target/52607] New: " marc.glisse at normalesup dot org
2012-03-17  4:58 ` [Bug target/52607] " marc.glisse at normalesup dot org
2012-03-17 19:55 ` marc.glisse at normalesup dot org
2012-03-17 20:11 ` marc.glisse at normalesup dot org
2012-03-17 22:17 ` marc.glisse at normalesup dot org
2012-03-18 14:51 ` marc.glisse at normalesup dot org
2012-03-18 20:13 ` marc.glisse at normalesup dot org
2012-03-19 11:16 ` jakub at gcc dot gnu.org
2012-03-19 17:19 ` jakub at gcc dot gnu.org
2012-03-19 19:00 ` marc.glisse at normalesup dot org
2012-03-19 19:29 ` jakub at gcc dot gnu.org
2012-03-19 20:09 ` rth at gcc dot gnu.org
2012-03-20  9:26 ` jakub at gcc dot gnu.org
2012-03-20 16:27 ` jakub at gcc dot gnu.org
2012-03-20 16:56 ` jakub at gcc dot gnu.org
2012-03-20 19:05 ` marc.glisse at normalesup dot org
2012-03-20 19:09 ` marc.glisse at normalesup dot org
2012-03-20 22:03 ` marc.glisse at normalesup dot org
2012-03-25 14:09 ` marc.glisse at normalesup dot org
2012-03-27 16:59 ` jakub at gcc dot gnu.org
2012-03-27 17:25 ` jakub at gcc dot gnu.org
2012-03-27 18:23 ` marc.glisse at normalesup dot org
2012-03-27 21:21 ` marc.glisse at normalesup dot org
2012-03-29 13:41 ` rth at gcc dot gnu.org
2012-03-29 14:20 ` marc.glisse at normalesup dot org
2012-03-31  9:49 ` marc.glisse at normalesup dot org
2012-03-31 14:12 ` marc.glisse at normalesup dot org
2012-04-09 16:51 ` marc.glisse at normalesup dot org
2012-04-11 16:49 ` marc.glisse at normalesup dot org [this message]
2012-04-11 20:35 ` marc.glisse at normalesup dot org
2012-05-14 21:29 ` glisse 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-52607-4-IVfofwiJqH@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: link
Be 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).