Re: [PATCH 0/6] More vector permutation work

2011-10-27 Thread Richard Henderson
On 10/27/2011 01:05 AM, Ulrich Weigand wrote: >> Richard Henderson wrote: >>> On 10/26/2011 07:30 AM, Ulrich Weigand wrote: This fails since for u == 4 and mode == V4SFmode it attempts to expand a V4SFmode shift, which is unsupported. Shouldn't this be using the mode of the sele

Re: [PATCH 0/6] More vector permutation work

2011-10-27 Thread Ulrich Weigand
> Richard Henderson wrote: > > On 10/26/2011 07:30 AM, Ulrich Weigand wrote: > > > This fails since for u == 4 and mode == V4SFmode it attempts to expand > > > a V4SFmode shift, which is unsupported. > > > > > > Shouldn't this be using the mode of the selector rather than the mode > > > of the res

Re: [PATCH 0/6] More vector permutation work

2011-10-26 Thread Iain Sandoe
On 26 Oct 2011, at 17:01, Richard Henderson wrote: On 10/26/2011 07:30 AM, Ulrich Weigand wrote: This fails since for u == 4 and mode == V4SFmode it attempts to expand a V4SFmode shift, which is unsupported. Shouldn't this be using the mode of the selector rather than the mode of the result

Re: [PATCH 0/6] More vector permutation work

2011-10-26 Thread Ulrich Weigand
Richard Henderson wrote: > On 10/26/2011 07:30 AM, Ulrich Weigand wrote: > > This fails since for u == 4 and mode == V4SFmode it attempts to expand > > a V4SFmode shift, which is unsupported. > > > > Shouldn't this be using the mode of the selector rather than the mode > > of the result in any cas

Re: [PATCH 0/6] More vector permutation work

2011-10-26 Thread Richard Henderson
On 10/26/2011 07:30 AM, Ulrich Weigand wrote: > This fails since for u == 4 and mode == V4SFmode it attempts to expand > a V4SFmode shift, which is unsupported. > > Shouldn't this be using the mode of the selector rather than the mode > of the result in any case? Yes, it should use the mode of th

Re: [PATCH 0/6] More vector permutation work

2011-10-26 Thread Ulrich Weigand
Richard Henderson wrote: > Fix typos in the names of vec_extract & vec_interleave tree codes. > Change vec_perm checking and expansion level. > Implement interleave via permutation. > spu: Remove vec_extract_even/odd and vec_interleave expanders. > rs6000: Remove some vec_extract_even/od

Re: [PATCH 0/6] More vector permutation work

2011-10-26 Thread Iain Sandoe
Hi Richard, On 25 Oct 2011, at 01:17, Richard Henderson wrote: The Idea with this patch set is to re-arrange vector permutation so that it can be used to implement other patterns automatically. In particular, Altivec, SPU currently have (and Sparc VIS would need) a large amount of boilerplate

Re: [PATCH 0/6] More vector permutation work

2011-10-25 Thread Richard Guenther
On Tue, Oct 25, 2011 at 2:17 AM, Richard Henderson wrote: > The Idea with this patch set is to re-arrange vector permutation > so that it can be used to implement other patterns automatically. > > In particular, Altivec, SPU currently have (and Sparc VIS would need) > a large amount of boilerplate

[PATCH 0/6] More vector permutation work

2011-10-24 Thread Richard Henderson
The Idea with this patch set is to re-arrange vector permutation so that it can be used to implement other patterns automatically. In particular, Altivec, SPU currently have (and Sparc VIS would need) a large amount of boilerplate code that transforms several higher level tree codes into vector pe