[Bug target/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake)

2020-09-11 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018

H.J. Lu  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
Summary|[10/11 Regression] FAIL:|[11 Regression] FAIL:
   |gcc.target/i386/l_fma_float |gcc.target/i386/l_fma_float
   |_1.c scan-assembler-times   |_1.c scan-assembler-times
   |vfnmsub[123]+ss 32 on   |vfnmsub[123]+ss 32 on
   |Linux/x86_64 (-m64  |Linux/x86_64 (-m64
   |-march=cascadelake) |-march=cascadelake)
 Resolution|--- |FIXED

--- Comment #7 from H.J. Lu  ---
(In reply to Sunil Pandey from comment #5)
> (In reply to Richard Biener from comment #1)
> > Do they PASS on the GCC 10 branch?
> 
> GCC 10 branch has same issue. Same patch should be applied to GCC 10 too.

They have been failing on GCC 10 branch for a while.  They aren't a recent
regression.  No plan to fix.

[Bug target/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake)

2020-09-11 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018

H.J. Lu  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
Version|11.0|10.2.0

--- Comment #6 from H.J. Lu  ---
GCC 10 has the same issue.

[Bug target/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake)

2020-09-11 Thread skpgkp2 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018

--- Comment #5 from Sunil Pandey  ---
(In reply to Richard Biener from comment #1)
> Do they PASS on the GCC 10 branch?

GCC 10 branch has same issue. Same patch should be applied to GCC 10 too.

[Bug target/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake)

2020-09-11 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018

H.J. Lu  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from H.J. Lu  ---
Fixed for GCC 11.

[Bug target/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake)

2020-09-11 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018

--- Comment #3 from CVS Commits  ---
The master branch has been updated by H.J. Lu :

https://gcc.gnu.org/g:40e99ed5f4e59c6d0a8e81cd6544c9b4e7ec2fe7

commit r11-3163-g40e99ed5f4e59c6d0a8e81cd6544c9b4e7ec2fe7
Author: Sunil K Pandey 
Date:   Thu Sep 10 23:17:59 2020 -0700

Fix fma test case [PR97018]

These tests are written for 256 bit vector. For -march=cascadelake,
vector size changed to 512 bit. It doubles the number of fma
instruction and test fail. Fix is to explicitly disable 512 bit
vector by passing additional option -mno-avx512f.

Tested on x86-64.

gcc/testsuite/ChangeLog:

PR target/97018
* gcc.target/i386/l_fma_double_1.c: Add option -mno-avx512f.
* gcc.target/i386/l_fma_double_2.c: Likewise.
* gcc.target/i386/l_fma_double_3.c: Likewise.
* gcc.target/i386/l_fma_double_4.c: Likewise.
* gcc.target/i386/l_fma_double_5.c: Likewise.
* gcc.target/i386/l_fma_double_6.c: Likewise.
* gcc.target/i386/l_fma_float_1.c: Likewise.
* gcc.target/i386/l_fma_float_2.c: Likewise.
* gcc.target/i386/l_fma_float_3.c: Likewise.
* gcc.target/i386/l_fma_float_4.c: Likewise.
* gcc.target/i386/l_fma_float_5.c: Likewise.
* gcc.target/i386/l_fma_float_6.c: Likewise.

[Bug target/97018] [11 Regression] FAIL: gcc.target/i386/l_fma_float_1.c scan-assembler-times vfnmsub[123]+ss 32 on Linux/x86_64 (-m64 -march=cascadelake)

2020-09-11 Thread crazylht at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97018

Hongtao.liu  changed:

   What|Removed |Added

 CC||crazylht at gmail dot com

--- Comment #2 from Hongtao.liu  ---
There's `-mtune=generic` in the testcase, which will imply 512-bit
vectorization on CLX, but testcase assume 256-bit vectorization.

Add `-mprefer-vector-width=256` or `-mno-avx512f`?