On Thu, Jan 26, 2017 at 11:54:52AM +0100, Uros Bizjak wrote:
> On Thu, Jan 26, 2017 at 11:51 AM, Jakub Jelinek <ja...@redhat.com> wrote:
> > On Thu, Jan 26, 2017 at 02:44:56AM -0800, Kirill Yukhin wrote:
> >> Hello Thomas,
> >> On 26 Jan 10:14, Thomas Schwinge wrote:
> >> > I see:
> >> >
> >> > {+FAIL: gcc.target/i386/avx512f-ktestw-2.c (test for excess errors)+}
> >> > {+UNRESOLVED: gcc.target/i386/avx512f-ktestw-2.c compilation failed
> >> > to produce executable+}
> >> >
> >> > ... because of:
> >> >
> >> > /tmp/ccjv3mX2.s: Assembler messages:
> >> > /tmp/ccjv3mX2.s:26: Error: no such instruction: `ktestw %k1,%k0'
> >> > compiler exited with status 1
> >> Which version of gas do you use?
> >> It should be OK since v2.25.
> >
> > It is weird, because the test already has:
> > /* { dg-require-effective-target avx512f } */
> > Perhaps if there are gas versions with partial avx512f support, we need
> > to improve the avx512f effective target test.
>
> This is actually AVX512DQ instruction, please see [1], 3-509.
>
> [1]
> https://software.intel.com/sites/default/files/managed/ad/01/253666-sdm-vol-2a.pdf
You're right. But then the tests should be named avx512dq-ktestw-{1,2}.c,
should use -mavx512dq, avx512dq effective target etc. and indeed the
intrinsics shouldn't be in avx512fintrin.h header, but dq, and should not be
enabled for f, but only dq.
Jakub
