Message ID | 357F7A5D-0FB5-41F9-8959-E9A3366A0D51@linux.vnet.ibm.com |
---|---|
State | New |
Headers | show |
On Thu, Jun 02, 2016 at 03:50:21PM -0500, Bill Schmidt wrote: > The only way I know to make the test predictable is to use a run-time test to check whether > P9 vector instructions will execute. Thus this solution. I’ve verified we no longer have test > failures on machines with a downlevel assembler, and the tests run correctly on machines > with an up-to-date assembler. Is this ok for trunk and 6.2? This is fine. Okay for both. Thanks, Segher
Index: gcc/testsuite/gcc.target/powerpc/vsx-elemrev-2.c =================================================================== --- gcc/testsuite/gcc.target/powerpc/vsx-elemrev-2.c (revision 237044) +++ gcc/testsuite/gcc.target/powerpc/vsx-elemrev-2.c (working copy) @@ -1,6 +1,7 @@ /* { dg-do compile { target { powerpc64le*-*-* } } } */ /* { dg-skip-if "do not override mcpu" { powerpc*-*-* } { "-mcpu=*" } { "-mcpu=power9" } } */ /* { dg-options "-mcpu=power9 -O0" } */ +/* { dg-require-effective-target p9vector_hw } */ /* { dg-final { scan-assembler-times "lxvd2x" 6 } } */ /* { dg-final { scan-assembler-times "lxvw4x" 6 } } */ /* { dg-final { scan-assembler-times "lxvh8x" 4 } } */ Index: gcc/testsuite/gcc.target/powerpc/vsx-elemrev-4.c =================================================================== --- gcc/testsuite/gcc.target/powerpc/vsx-elemrev-4.c (revision 237044) +++ gcc/testsuite/gcc.target/powerpc/vsx-elemrev-4.c (working copy) @@ -1,6 +1,7 @@ /* { dg-do compile { target { powerpc64-*-* } } } */ /* { dg-skip-if "do not override mcpu" { powerpc*-*-* } { "-mcpu=*" } { "-mcpu=power9" } } */ /* { dg-options "-mcpu=power9 -O0" } */ +/* { dg-require-effective-target p9vector_hw } */ /* { dg-final { scan-assembler-times "lxvx" 40 } } */ /* { dg-final { scan-assembler-times "stxvx" 40 } } */