Hi, For a long time we've had hundreds of failing guality tests. These failures don't seem to have any correlation with gdb functionality for POWER, which is working fine. At this point the value of these tests to us seems questionable. Fixing these is such low priority that it is unlikely we will ever get around to it. In the meanwhile, the failures simply clutter up our regression test reports. Thus I'd like to disable them, and that's what this test does.
Verified to remove hundreds of failure messages on powerpc64le-unknown-linux-gnu. :) Is this ok for trunk? Thanks, Bill 2016-03-28 Bill Schmidt <wschm...@linux.vnet.ibm.com> * g++.dg/guality/guality.exp: Disable for powerpc*-linux*. * gcc.dg/guality/guality.exp: Likewise. Index: gcc/testsuite/g++.dg/guality/guality.exp =================================================================== --- gcc/testsuite/g++.dg/guality/guality.exp (revision 234476) +++ gcc/testsuite/g++.dg/guality/guality.exp (working copy) @@ -13,6 +13,11 @@ if { [istarget "powerpc-ibm-aix*"] } { return } +if { [istarget "powerpc*-linux*"] } { + set torture_execute_xfail "powerpc*-linux*" + return +} + proc check_guality {args} { # Don't count check_guality as PASS, or FAIL etc., that would make # the total PASS count dependent on how many parallel runtest invocations Index: gcc/testsuite/gcc.dg/guality/guality.exp =================================================================== --- gcc/testsuite/gcc.dg/guality/guality.exp (revision 234476) +++ gcc/testsuite/gcc.dg/guality/guality.exp (working copy) @@ -13,6 +13,11 @@ if { [istarget "powerpc-ibm-aix*"] } { return } +if { [istarget "powerpc*-linux*"] } { + set torture_execute_xfail "powerpc*-linux*" + return +} + proc check_guality {args} { # Don't count check_guality as PASS, or FAIL etc., that would make # the total PASS count dependent on how many parallel runtest invocations