diff options
| author | Will Schmidt <will_schmidt@vnet.ibm.com> | 2020-09-09 10:59:38 -0500 |
|---|---|---|
| committer | Will Schmidt <will_schmidt@vnet.ibm.com> | 2020-09-11 15:47:20 -0500 |
| commit | 2fda9e9badbd78d1033075a44a7d6c1b33de239c (patch) | |
| tree | ab98cb069bf91a8e30087b47cd711f8d13c8cf82 /gcc/function.c | |
| parent | 2c3b1c5f950429c05865c88bc0b4a460d23f5192 (diff) | |
| download | gcc-2fda9e9badbd78d1033075a44a7d6c1b33de239c.zip gcc-2fda9e9badbd78d1033075a44a7d6c1b33de239c.tar.gz gcc-2fda9e9badbd78d1033075a44a7d6c1b33de239c.tar.bz2 | |
[PATCH,rs6000] Testsuite fixup pr96139 tests
Hi,
As reported, the recently added pr96139 tests will fail on older targets
because the tests are missing the appropriate -mvsx or -maltivec options.
This adds the options and clarifies the dg-require statements.
The pr96139-c.c test needs -maltivec to work, but does not actually use
vectors, so does not require -mvsx like the others.
Sniff-regtested OK when specifying older targets on a power7 host.
--target_board=unix/'{-mcpu=power4,-mcpu=power5,-mcpu=power6,-mcpu=power7,
-mcpu=power8,-mcpu=power9}''{-m64,-m32}'"
gcc/testsuite/ChangeLog:
* gcc.target/powerpc/pr96139-a.c: Specify -mvsx option and update the
dg-require stanza to match.
* gcc.target/powerpc/pr96139-b.c: Same.
* gcc.target/powerpc/pr96139-c.c: Specify -maltivec option and update
the dg-require stanza to match.
Diffstat (limited to 'gcc/function.c')
0 files changed, 0 insertions, 0 deletions