diff options
| author | Uros Bizjak <ubizjak@gmail.com> | 2024-02-14 21:09:35 +0100 |
|---|---|---|
| committer | Uros Bizjak <ubizjak@gmail.com> | 2024-02-14 21:10:31 +0100 |
| commit | 430c772be3382134886db33133ed466c02efc71c (patch) | |
| tree | 074ef20e9c20acd7b8b2fa54538a34a35dc97822 /gcc/fortran/trans-decl.cc | |
| parent | 67ce5c97167a60cb845b9f3f55186c00fc5df078 (diff) | |
| download | gcc-430c772be3382134886db33133ed466c02efc71c.zip gcc-430c772be3382134886db33133ed466c02efc71c.tar.gz gcc-430c772be3382134886db33133ed466c02efc71c.tar.bz2 | |
testsuite: Fix a couple of x86 issues in gcc.dg/vect testsuite
A compile-time test can use -march=skylake-avx512 for all x86 targets,
but a runtime test needs to check avx512f effective target if the
instructions can be assembled.
The runtime test also needs to check if the target machine supports
instruction set we have been compiled for. The testsuite uses check_vect
infrastructure, but handling of AVX512F+ ISAs was missing there.
Add detection of __AVX512F__ and __AVX512VL__, which is enough to handle
all currently mentioned target processors in the gcc.dg/vect testsuite.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr113576.c (dg-additional-options):
Use -march=skylake-avx512 for avx512f effective target.
* gcc.dg/vect/pr98308.c (dg-additional-options):
Use -march=skylake-avx512 for all x86 targets.
* gcc.dg/vect/tree-vect.h (check_vect): Handle __AVX512F__
and __AVX512VL__.
Diffstat (limited to 'gcc/fortran/trans-decl.cc')
0 files changed, 0 insertions, 0 deletions