> Here's what I had in my local tree during last weekend's bootstraps: it
> worked fine indeed.
>
> Rainer
>
>
> 2015-01-23 Rainer Orth
>
> * lib/target-supports.exp (check_effective_target_vect64): Add
> sparc*-*-*.
Fine with me then, thanks.
--
Eric Botcazou
Richard Biener writes:
> On Mon, 26 Jan 2015, Eric Botcazou wrote:
>
>> > For the second half we really need to fix SPARC to be a vect64
>> > target (the testcase is vectorized with v8qi).
>>
>> Yes, that makes sense in conjunction with the options used for vectorization.
>
> As I can't test spa
On Mon, 26 Jan 2015, Eric Botcazou wrote:
> > For the second half we really need to fix SPARC to be a vect64
> > target (the testcase is vectorized with v8qi).
>
> Yes, that makes sense in conjunction with the options used for vectorization.
As I can't test sparc can you or rainer do the change
> For the second half we really need to fix SPARC to be a vect64
> target (the testcase is vectorized with v8qi).
Yes, that makes sense in conjunction with the options used for vectorization.
--
Eric Botcazou
The following should fix gcc.dg/vect/vect-33.c failing on arm
by properly guarding the scan-tree-dumps for vect64 tagets that
also can vectorize with v16qi. I've choosen to use
vect_multiple_sizes for that, hoping we don't have targets
that do vect32.
Reliably writing vectorizer testcases gets h
