diff options
author | Douglas Rupp <rupp@adacore.com> | 2020-05-18 11:43:48 -0700 |
---|---|---|
committer | Joel Brobecker <brobecker@adacore.com> | 2020-05-18 11:43:48 -0700 |
commit | c917584aa9ec32934acf0082ed383b04f49fd174 (patch) | |
tree | 7a0f4b9589fd7063d28b89b5738b639afe03c753 /gcc/tree-object-size.c | |
parent | 5329b59a2e13dabbe2038af0fe2e3cf5fc7f98ed (diff) | |
download | gcc-c917584aa9ec32934acf0082ed383b04f49fd174.zip gcc-c917584aa9ec32934acf0082ed383b04f49fd174.tar.gz gcc-c917584aa9ec32934acf0082ed383b04f49fd174.tar.bz2 |
Require powerpc_vsx_ok in gcc.target/powerpc/pr71763.c
We're getting an error when running this test on PowerPC VxWorks 7,
due to an unexpected warning:
| Excess errors:
| cc1: warning: '-mvsx' and '-mno-altivec' are incompatible
The warning comes from a combination of factors:
- The test itself uses -mvsx explicitly via the following directive:
// { dg-options "-O1 -mvsx" }
- Our toolchain was configured so as to make -mno-altivec
the default;
- These two options are mutually exclusive.
This commit adds a powerpc_vsx_ok dg-require-effective-target directive
to that test, and thus making it UNSUPPORTED instead.
Tested on PowerPC VxWorks 7. Also tested on PowerPC ELF as well,
a platform where we do not make -mno-altivec the default, to verify
that the test continues to run as usual in that case.
gcc/testsuite/
* gcc.target/powerpc/pr71763.c: Require powerpc_vsx_ok.
Diffstat (limited to 'gcc/tree-object-size.c')
0 files changed, 0 insertions, 0 deletions