Hi,
Noticed during review of test results. I expect the intent
here was to compile in cases where the run command was not
valid.
But for the scan-assembler stanza to work, need to have compile results
in all cases.
/* { dg-do run { target { powerpc*-*-* && vmx_hw } } } */
/* { dg-do compile { target { powerpc*-*-* && { ! vmx_hw } } } } */
/* { dg-require-effective-target powerpc_altivec_ok } */
...
/* { dg-final { scan-assembler-not "lvx" { target { powerpc*le-*-* } } } } */
So..
Added some commentary, updated the stanzas, retested on assorted power systems.
This fixes "scan-assembler-not lvx" failure as seen in testresults from LE
systems.
OK for trunk?
Thanks
-Will
[testsuite]
2018-02-12 Will Schmidt <[email protected]>
* gcc.target/powerpc/altivec-consts.c: Update compile stanzas.
* gcc.target/powerpc/le-altivec-consts.c: Same.
diff --git a/gcc/testsuite/gcc.target/powerpc/altivec-consts.c
b/gcc/testsuite/gcc.target/powerpc/altivec-consts.c
index 36cb60c..8ec73e9 100644
--- a/gcc/testsuite/gcc.target/powerpc/altivec-consts.c
+++ b/gcc/testsuite/gcc.target/powerpc/altivec-consts.c
@@ -1,7 +1,11 @@
+/* altivec-consts.c:
+ Requires vmx_hw support to run. Requires altivec support to compile.
+ This test varies from le-altivec-consts.c in the ordering of the
+ vector elements below. */
/* { dg-do run { target { powerpc*-*-* && vmx_hw } } } */
-/* { dg-do compile { target { powerpc*-*-* && { ! vmx_hw } } } } */
+/* { dg-do compile { target { powerpc*-*-* } } } */
/* { dg-require-effective-target powerpc_altivec_ok } */
/* { dg-options "-maltivec -mabi=altivec -O2" } */
/* Check that "easy" AltiVec constants are correctly synthesized. */
diff --git a/gcc/testsuite/gcc.target/powerpc/le-altivec-consts.c
b/gcc/testsuite/gcc.target/powerpc/le-altivec-consts.c
index 15ec650..2f81ff7 100644
--- a/gcc/testsuite/gcc.target/powerpc/le-altivec-consts.c
+++ b/gcc/testsuite/gcc.target/powerpc/le-altivec-consts.c
@@ -1,7 +1,11 @@
+/* le-altivec-consts.c:
+ Requires vmx_hw support to run. Requires altivec support to compile.
+ This test varies from altivec-consts.c in the ordering of the
+ vector elements below. */
/* { dg-do run { target { powerpc*-*-* && vmx_hw } } } */
-/* { dg-do compile { target { powerpc*-*-* && { ! vmx_hw } } } } */
+/* { dg-do compile { target { powerpc*-*-* } } } */
/* { dg-require-effective-target powerpc_altivec_ok } */
/* { dg-options "-maltivec -mabi=altivec -O2" } */
/* Check that "easy" AltiVec constants are correctly synthesized. */