On Tue, 6 Jan 2026, Rainer Orth wrote: > Two tests FAIL on 32 and 64-bit SPARC: > > FAIL: gcc.dg/vect/vect-bool-2.c scan-tree-dump vect "optimized: loop > vectorized" > FAIL: gcc.dg/vect/vect-bool-cmp-4.c scan-tree-dump vect "optimized: loop > vectorized" > > The dump shows > > gcc.dg/vect/vect-bool-2.c:12:12: missed: not vectorized: relevant stmt not > supported: y_7 = _1 <= 16; > > so the test needs vect_bool_cmp.
<= 16 suggests a comparison in type char, not bool tough. There's no effective target for compares in general it seems? But indeed we might read that as "QImode compare"? Given that's what vect-bool-cmp-2.c requires for example. That also requires bool-cmp mask to bool vec_cond_mask. It would be so nice if the effective target names would map to optabs (or combinations of those). So... > Tested on sparc-sun-solaris2.11 and i386-pc-solaris2.11. > > Ok for trunk? OK. Richard. > Rainer > > -- Richard Biener <[email protected]> SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany; GF: Jochen Jaser, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
