This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Fix __mmask* types on many AVX512 intrinsics
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Grazvydas Ignotas <notasas at gmail dot com>
- Cc: Kirill Yukhin <kirill dot yukhin at gmail dot com>, Uros Bizjak <ubizjak at gmail dot com>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 9 Jul 2018 09:37:14 +0200
- Subject: Re: [PATCH] Fix __mmask* types on many AVX512 intrinsics
- References: <1530811827-12303-1-git-send-email-notasas@gmail.com> <20180705182819.GL7166@tucnak> <CANOLnOM2ZAsZ8RjpsjuDAQBRyyFj1TeVOVgjXhOGY74XE69ZWw@mail.gmail.com> <20180706104707.GM7166@tucnak> <20180707081550.GQ7166@tucnak> <CANOLnONy=q_Y4Y_eikoq_FcDq60uo58DkgBFPwpaqmH9T_ou8g@mail.gmail.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Sun, Jul 08, 2018 at 02:39:40AM +0300, Grazvydas Ignotas wrote:
> > I guess we want to backport it soon, but would appreciate somebody testing
> > it on real AVX512-{BW,VL} hw before doing the backports.
>
> I've run the testsuite with this patch applied and all tests passed on
> i7-7800X.
Thanks for the testing.
> There are avx512vl-vmovdqa64-1.c and avx512vl-vpermilpdi-1.c
> failures, but those seem unrelated.
These are dg-do compile tests, and they PASS for me, even when doing
make check-gcc RUNTESTFLAGS="--target_board=unix/-march=skylake-avx512 i386.exp='avx512vl-vmovdqa64-1.c avx512vl-vpermilpdi-1.c'"
So, how exactly you've configured your gcc, what kind of options are
passed to the test and how they FAIL?
Jakub