public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "agner at agner dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52932] AVX2 intrinsic _mm256_permutevar8x32_ps has wrong parameter type
Date: Fri, 13 Apr 2012 16:51:00 -0000 [thread overview]
Message-ID: <bug-52932-4-XiZ52v3ZtI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52932-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52932
--- Comment #10 from Agner Fog <agner at agner dot org> 2012-04-13 16:50:33 UTC ---
_mm256_permutevar8x32_epi32 has the operands in wrong order. They need
to be swapped. Did you fix this too?
On 12-04-2012 20:37, uros at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52932
>
> --- Comment #9 from uros at gcc dot gnu.org 2012-04-12 18:37:47 UTC ---
> Author: uros
> Date: Thu Apr 12 18:37:42 2012
> New Revision: 186388
>
> URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=186388
> Log:
> PR target/52932
> * config/i386/avx2intrin.h (_mm256_permutevar8x32_ps): Change second
> argument type to __m256i. Update call to __builtin_ia32_permvarsf256.
> * config/i386/sse.md (UNSPEC_VPERMVAR): New.
> (UNSPEC_VPERMSI, UNSPEC_VPERMSF): Remove.
> (avx2_permvarv8sf, avx2_permvarv8si): Switch operands 1 and 2.
> (avx2_permvar<mode>): Macroize insn from avx2_permvarv8sf and
> avx2_permvarv8si using VI4F_256 mode iterator.
> * config/i386/i386.c (bdesc_args)<__builtin_ia32_permvarsf256>:
> Update builtin type to V8SF_FTYPE_V8SF_V8SI.
> (ix86_expand_vec_perm): Update calls to gen_avx2_permvarv8si and
> gen_avx2_permvarv8sf.
> (expand_vec_perm_pshufb): Ditto.
>
> testsuite/ChangeLog:
>
> PR target/52932
> * gcc.target/i386/avx2-vpermps-1.c (avx2_test): Use __m256i type for
> second function argument.
> * gcc.target/i386/avx2-vpermps-2.c (init_permps): Update declaration.
> (calc_permps): Update declaration. Calculate result correctly.
> (avx2_test): Change src2 type to union256i_d.
> * gcc.target/i386/avx2-vpermd-2.c (calc_permd): Calculate result
> correctly.
>
>
> Modified:
> trunk/gcc/ChangeLog
> trunk/gcc/config/i386/avx2intrin.h
> trunk/gcc/config/i386/i386.c
> trunk/gcc/config/i386/sse.md
> trunk/gcc/testsuite/ChangeLog
> trunk/gcc/testsuite/gcc.target/i386/avx2-vpermd-2.c
> trunk/gcc/testsuite/gcc.target/i386/avx2-vpermps-1.c
> trunk/gcc/testsuite/gcc.target/i386/avx2-vpermps-2.c
>
next prev parent reply other threads:[~2012-04-13 16:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:25 [Bug c/52932] New: " agner at agner dot org
2012-04-11 14:12 ` [Bug c/52932] " ubizjak at gmail dot com
2012-04-11 14:16 ` [Bug target/52932] " ubizjak at gmail dot com
2012-04-11 14:16 ` [Bug c/52932] " ubizjak at gmail dot com
2012-04-11 17:32 ` [Bug target/52932] " kirill.yukhin at intel dot com
2012-04-12 13:53 ` kirill.yukhin at intel dot com
2012-04-12 13:54 ` kirill.yukhin at intel dot com
2012-04-12 13:58 ` ubizjak at gmail dot com
2012-04-12 17:08 ` ubizjak at gmail dot com
2012-04-12 17:11 ` ubizjak at gmail dot com
2012-04-12 18:39 ` uros at gcc dot gnu.org
2012-04-13 16:51 ` agner at agner dot org [this message]
2012-04-13 16:58 ` ubizjak at gmail dot com
2012-04-13 18:10 ` ubizjak at gmail dot com
2012-04-16 16:04 ` uros at gcc dot gnu.org
2012-04-16 16:05 ` ubizjak 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-52932-4-XiZ52v3ZtI@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).