The dg-do directive appears after dg-require-effective-target in
g++.target/powerpc/pr106069.C. That doesn't work the way that was
presumably intended. Both of these directives set dg-do-what, but
dg-do does so fully and unconditionally, overriding any decisions
recorded there by earlier directives. Reorder the directives more
canonically, so that both take effect.
for gcc/testsuite/ChangeLog
PR target/106069
* g++.target/powerpc/pr106069.C: Reorder dg directives.
(cherry picked from commit
ad65caa332bc7600caff6b9b5b29175b40d91e67)
+/* { dg-do run } */
/* { dg-options "-O -fno-tree-forwprop -maltivec" } */
/* { dg-require-effective-target vmx_hw } */
-/* { dg-do run } */
typedef __attribute__ ((altivec (vector__))) unsigned native_simd_type;