| Message ID | 1517426980.11602.247.camel@brimstone.rchland.ibm.com |
|---|---|
| State | New |
| Headers | show |
| Series | [rs6000] Update dg-requires for P9 specific tests. | expand |
Hi! On Wed, Jan 31, 2018 at 01:29:40PM -0600, Will Schmidt wrote: > Noticed during a review of test results on an AIX platform, a few > of the (p9 target specific) tests are expecting to see Power9 codegen, but > are failing to build due to the environment missing P9 assembler support. Thus, > we need to add the power9_vector_ok test requirement to these tests. Thanks for doing this! Okay for trunk (and backports if needed). Segher > 2018-01-31 Will Schmidt <will_schmidt@vnet.ibm.com> > > * gcc.target/powerpc/fold-vec-abs-int.p9.c: Add powerpc_p9vector_ok > requirement. > * gcc.target/powerpc/fold-vec-abs-int-fwrapv.p9.c: Same. > * gcc.target/powerpc/fold-vec-cmp-char.p9.c: Same. > * gcc.target/powerpc/fold-vec-neg-int.p9.c: Same.
diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int-fwrapv.p9.c b/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int-fwrapv.p9.c index cde86b8..87e0972 100644 --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int-fwrapv.p9.c +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int-fwrapv.p9.c @@ -1,10 +1,10 @@ /* Verify that overloaded built-ins for vec_abs with int inputs produce the right results when -mcpu=power9 is specified. */ /* { dg-do compile } */ -/* { dg-require-effective-target powerpc_altivec_ok } */ +/* { dg-require-effective-target powerpc_p9vector_ok } */ /* { dg-options "-maltivec -O2 -mcpu=power9 -fwrapv" } */ /* { dg-skip-if "do not override -mcpu" { powerpc*-*-* } { "-mcpu=*" } { "-mcpu=power9" } } */ #include <altivec.h> diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int.p9.c b/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int.p9.c index 6f2c686..c36ba2b 100644 --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int.p9.c +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-abs-int.p9.c @@ -1,10 +1,10 @@ /* Verify that overloaded built-ins for vec_abs with int inputs produce the right code when -mcpu=power9 is specified. */ /* { dg-do compile } */ -/* { dg-require-effective-target powerpc_altivec_ok } */ +/* { dg-require-effective-target powerpc_p9vector_ok } */ /* { dg-options "-maltivec -O2 -mcpu=power9" } */ /* { dg-skip-if "do not override -mcpu" { powerpc*-*-* } { "-mcpu=*" } { "-mcpu=power9" } } */ #include <altivec.h> diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-cmp-char.p9.c b/gcc/testsuite/gcc.target/powerpc/fold-vec-cmp-char.p9.c index e3ff89c..1998443 100644 --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-cmp-char.p9.c +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-cmp-char.p9.c @@ -1,10 +1,10 @@ /* Verify that overloaded built-ins for vec_cmp{eq,ge,gt,le,lt,ne} with char inputs produce the right code when -mcpu=power9 is specified. */ /* { dg-do compile } */ -/* { dg-require-effective-target powerpc_p8vector_ok } */ +/* { dg-require-effective-target powerpc_p9vector_ok } */ /* { dg-options "-mpower8-vector -mcpu=power9 -O2" } */ /* { dg-skip-if "do not override -mcpu" { powerpc*-*-* } { "-mcpu=*" } { "-mcpu=power9" } } */ #include "fold-vec-cmp-char.h" diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.p9.c b/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.p9.c index 44732c8..7da8773 100644 --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.p9.c +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-neg-int.p9.c @@ -1,10 +1,10 @@ /* Verify that overloaded built-ins for vec_neg with int inputs produce the right code when -mcpu=power9 is specified. */ /* { dg-do compile } */ -/* { dg-require-effective-target powerpc_altivec_ok } */ +/* { dg-require-effective-target powerpc_p9vector_ok } */ /* { dg-options "-maltivec -O2 -mcpu=power9" } */ /* { dg-skip-if "do not override -mcpu" { powerpc*-*-* } { "-mcpu=*" } { "-mcpu=power9" } } */ #include <altivec.h>
Hi, Noticed during a review of test results on an AIX platform, a few of the (p9 target specific) tests are expecting to see Power9 codegen, but are failing to build due to the environment missing P9 assembler support. Thus, we need to add the power9_vector_ok test requirement to these tests. Sniff-test passes on gcc119. OK for trunk? Thanks, -Will [testsuite] 2018-01-31 Will Schmidt <will_schmidt@vnet.ibm.com> * gcc.target/powerpc/fold-vec-abs-int.p9.c: Add powerpc_p9vector_ok requirement. * gcc.target/powerpc/fold-vec-abs-int-fwrapv.p9.c: Same. * gcc.target/powerpc/fold-vec-cmp-char.p9.c: Same. * gcc.target/powerpc/fold-vec-neg-int.p9.c: Same.