[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

H.J. Lu  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #13 from H.J. Lu  ---
Fixed.

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-02-11 Thread kyukhin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #12 from Kirill Yukhin  ---
Author: kyukhin
Date: Mon Feb 12 06:14:15 2018
New Revision: 257579

URL: https://gcc.gnu.org/viewcvs?rev=257579=gcc=rev
Log:
Fix AVX-512 popcnt and bitalg tests.

gcc/testsuite/
PR target/83828
* gcc.target/i386/avx512bitalg-vpopcntb-1.c: Fix test.
* gcc.target/i386/avx512bitalg-vpopcntw-1.c: Ditto.
* gcc.target/i386/avx512bitalg-vpshufbitqmb-1.c: Ditto.
* gcc.target/i386/avx512vpopcntdq-vpopcntd-1.c: Ditto.
* gcc.target/i386/avx512vpopcntdq-vpopcntq-1.c: Ditto.

Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/i386/avx512bitalg-vpopcntb-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bitalg-vpopcntw-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bitalg-vpshufbitqmb-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512vpopcntdq-vpopcntd-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512vpopcntdq-vpopcntq-1.c

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-02-06 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #11 from H.J. Lu  ---
(In reply to Kirill Yukhin from comment #10)
> HJ, I cannot reproduce this fail on recent SDE.
> 
> Here's what I have in gcc.log:
> 
> spawn -ignore SIGHUP /export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc/xgcc
> -B/export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc/
> /export/kyukhin/gcc/svn/trunk/gcc/testsuite/gcc.target/i386/avx512bitalgvl-
> vpopc\
> ntb-1.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O2 -mavx512vl
> -mavx512bitalg -mavx512bw -lm -o ./avx512bitalgvl-vpopcntb-1.exe^M
> PASS: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c (test for excess errors)
> Setting LD_LIBRARY_PATH to
> :/export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc:/export/kyukhin/gcc/bld-
> svn/build-x86_64-linux/gcc/32:
> spawn /home/kyukhin/bin/dejagnu/sde-sim ./avx512bitalgvl-vpopcntb-1.exe^M
> PASS: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c execution test
> 
> I've also verified manually that test PASS, not SKIPPED.

You can't reproduce it with SDE since it emulates the new AVX512 instructions.
Olga posted a patch at:

https://gcc.gnu.org/ml/gcc-patches/2018-02/msg00209.html

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-02-05 Thread kyukhin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #10 from Kirill Yukhin  ---
HJ, I cannot reproduce this fail on recent SDE.

Here's what I have in gcc.log:

spawn -ignore SIGHUP /export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc/xgcc
-B/export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc/
/export/kyukhin/gcc/svn/trunk/gcc/testsuite/gcc.target/i386/avx512bitalgvl-vpopc\
ntb-1.c -fno-diagnostics-show-caret -fdiagnostics-color=never -O2 -mavx512vl
-mavx512bitalg -mavx512bw -lm -o ./avx512bitalgvl-vpopcntb-1.exe^M
PASS: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c (test for excess errors)
Setting LD_LIBRARY_PATH to
:/export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc:/export/kyukhin/gcc/bld-svn/build-x86_64-linux/gcc/32:
spawn /home/kyukhin/bin/dejagnu/sde-sim ./avx512bitalgvl-vpopcntb-1.exe^M
PASS: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c execution test

I've also verified manually that test PASS, not SKIPPED.

Could you pls send some more info on failure?

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-30 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #9 from H.J. Lu  ---
r257175 gave:

FAIL: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c execution test
FAIL: gcc.target/i386/avx512bitalgvl-vpopcntw-1.c execution test
FAIL: gcc.target/i386/avx512bitalg-vpopcntb-1.c execution test
FAIL: gcc.target/i386/avx512bitalg-vpopcntw-1.c execution test

on AVX512 machine.

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-30 Thread kyukhin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #8 from Kirill Yukhin  ---
Author: kyukhin
Date: Tue Jan 30 08:21:22 2018
New Revision: 257173

URL: https://gcc.gnu.org/viewcvs?rev=257173=gcc=rev
Log:
Fix AVX-512BITALG test failures

gcc/testsuite
PR target/83828
* gcc.target/i386/avx512bitalg-vpopcntb-1.c: Fix test.
* gcc.target/i386/avx512bitalg-vpopcntw-1.c: Ditto.
* gcc.target/i386/avx512bitalgvl-vpopcntb-1.c: Ditto.
* gcc.target/i386/avx512bitalgvl-vpopcntw-1.c: Ditto.


Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/i386/avx512bitalg-vpopcntb-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bitalg-vpopcntw-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bitalgvl-vpopcntb-1.c
trunk/gcc/testsuite/gcc.target/i386/avx512bitalgvl-vpopcntw-1.c

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-29 Thread kyukhin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #7 from Kirill Yukhin  ---
On the other hand, if masked variant of vpopcnt[w,q] is being issued: there's
no way for reload to put 32/64 bit mask into mask register, since kmov[d,q] are
only available  under -mavx512bw switch.

We can insist user to issue -mavx512bw along w/ -mavx512bitalg if she is going
to use masked variants of corresponding intrinsics. Then only tests need to be
fixed.

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-29 Thread kyukhin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

Kirill Yukhin  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||kyukhin at gcc dot gnu.org

--- Comment #6 from Kirill Yukhin  ---
Looks like avx512bw demand is excessive in avx512bitalgintrin.h

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-28 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

H.J. Lu  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-01-28
 Ever confirmed|0   |1

--- Comment #5 from H.J. Lu  ---
Need binutils 2.30 to reproduce.

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-28 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

H.J. Lu  changed:

   What|Removed |Added

 CC||ro at gcc dot gnu.org

--- Comment #4 from H.J. Lu  ---
*** Bug 84081 has been marked as a duplicate of this bug. ***

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-27 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #3 from H.J. Lu  ---
On AVX512 machine, r257121 gave:

FAIL: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c (test for excess errors)
FAIL: gcc.target/i386/avx512bitalgvl-vpopcntb-1.c (test for excess errors)
FAIL: gcc.target/i386/avx512bitalgvl-vpopcntw-1.c execution test
FAIL: gcc.target/i386/avx512bitalgvl-vpopcntw-1.c execution test
FAIL: gcc.target/i386/avx512bitalgvl-vpshufbitqmb-1.c execution test
FAIL: gcc.target/i386/avx512bitalgvl-vpshufbitqmb-1.c execution test

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-15 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

Richard Biener  changed:

   What|Removed |Added

   Keywords||wrong-code
 Target||x86_64-*-*, i?86-*-*

--- Comment #2 from Richard Biener  ---
Either wrong-code or testsuite issue.

[Bug target/83828] FAIL: gcc.target/i386/avx512vpopcntdqvl-vpopcntq-1.c execution test

2018-01-14 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83828

--- Comment #1 from H.J. Lu  ---
On GCC 7 branch, I got

FAIL: gcc.target/i386/avx512vl-vpermb-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpermb-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpermi2b-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpermi2b-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpermt2b-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpermt2b-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpmaddhuq-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpmaddhuq-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpmaddluq-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpmaddluq-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpmultishiftqb-2.c execution test
FAIL: gcc.target/i386/avx512vl-vpmultishiftqb-2.c execution test