This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/52607] v4df __builtin_shuffle with {0,2,1,3} or {1,3,0,2}
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 27 Mar 2012 17:10:00 +0000
- Subject: [Bug target/52607] v4df __builtin_shuffle with {0,2,1,3} or {1,3,0,2}
- Auto-submitted: auto-generated
- References: <bug-52607-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52607
--- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-03-27 17:10:00 UTC ---
Thanks for working on this.
I don't like much the calls to ix86_expand_vec_perm_const_1, if you are looking
for exactly two insn permutations, then really the two insn permutation
functions should be groupped together into expand_vec_perm_2 and you should
call that instead, or if it is 1 or 2, then expand_vec_perm_1 ||
expand_vec_perm_2.
expand_vec_perm_vperm2f128_merge has probably swapped the meaning of dfirst and
dsecond permutations when it first performs the dsecond permutation.
Lastly for each routine it is desirable to think whether it might be useful for
other vector modes (likely 32-byte only) for TARGET_AVX2.