https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114072
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> --- [...] >> I think the best we can do then is >> >> /* { dg-skip-if "PR tree-optimization/114072" { be && { ! vect_shift_char } >> } } >> */ >> >> Lets the test become UNSUPPORTED on 32 and 64-bit SPARC, but still PASS >> as before on 32 and 64-bit x86. > > Can we instead guard the scan-tree-dump? This way the correctness > execute part still is exercised? Sure, even if the result is somewhat hard to read with all those levels of braces: /* { dg-final { scan-tree-dump "LOOP VECTORIZED" "vect" { target { vect_int && { le || { be && vect_shift_char } } } } } } */ This way, all of compile, execute, and scan are run on x86, while on sparc it's only compile, execute.