On Fri, Oct 17, 2014 at 2:57 PM, Jakub Jelinek wrote:
> On Fri, Oct 17, 2014 at 04:28:12PM +0400, Kirill Yukhin wrote:
>> > I wonder whether for these modes it can ever be beneficial to build them
>> > through interleaves/concatenations etc., if it wouldn't be better to build
>> > them by storing
On Fri, Oct 17, 2014 at 04:28:12PM +0400, Kirill Yukhin wrote:
> > I wonder whether for these modes it can ever be beneficial to build them
> > through interleaves/concatenations etc., if it wouldn't be better to build
> > them by storing all values into memory and just reading it back.
> I've trie
Hello Jakub,
On 15 Oct 18:23, Jakub Jelinek wrote:
> On Thu, Oct 09, 2014 at 04:13:25PM +0400, Kirill Yukhin wrote:
> > --- a/gcc/config/i386/i386.c
> > +++ b/gcc/config/i386/i386.c
> > @@ -39821,6 +39823,9 @@ ix86_expand_vector_init_duplicate (bool mmx_ok,
> > enum machine_mode mode,
> >g
On Thu, Oct 09, 2014 at 04:13:25PM +0400, Kirill Yukhin wrote:
> --- a/gcc/config/i386/i386.c
> +++ b/gcc/config/i386/i386.c
> @@ -39791,6 +39791,8 @@ ix86_expand_vector_init_duplicate (bool mmx_ok, enum
> machine_mode mode,
> case V8SFmode:
> case V8SImode:
> case V2DFmode:
> +
On Thu, Oct 9, 2014 at 2:13 PM, Kirill Yukhin wrote:
> Hello,
> This patch extends vec_init-related routines/patterns.
>
> Bootstrapped.
> AVX-512* tests on top of patch-set all pass
> under simulator.
>
> Is it ok for trunk?
>
> gcc/
> * config/i386/i386.c
> (ix86_expand_vector_in
Hello,
This patch extends vec_init-related routines/patterns.
Bootstrapped.
AVX-512* tests on top of patch-set all pass
under simulator.
Is it ok for trunk?
gcc/
* config/i386/i386.c
(ix86_expand_vector_init_duplicate): Handle V64QI and V32HI modes,
update V8HI, V16QI, V3
