On Tue, 28 Feb 2012, Jakub Jelinek wrote:
> On Tue, Feb 28, 2012 at 02:01:45PM +0100, Richard Guenther wrote:
> > I guess using __INT64_TYPE__ is more portable to weird targets
> > though. I integrated the other testcase changes though.
>
> To which weird targets? We support long long on all ta
On Tue, Feb 28, 2012 at 02:01:45PM +0100, Richard Guenther wrote:
> I guess using __INT64_TYPE__ is more portable to weird targets
> though. I integrated the other testcase changes though.
To which weird targets? We support long long on all targets,
and the C standard guarantees it is at least 6
On Tue, 28 Feb 2012, Uros Bizjak wrote:
> Hello!
>
> > This fixes element ordering for V2SFmode, V2SImode and V2DImode
> > concats in ix86_expand_vector_set.
> >
> > Boostrap / regtest pending on x86_64-unknown-linux-gnu.
> >
> > Ok everywhere? (the testcase only fails on trunk)
> >
> > 2012-02-
Hello!
> This fixes element ordering for V2SFmode, V2SImode and V2DImode
> concats in ix86_expand_vector_set.
>
> Boostrap / regtest pending on x86_64-unknown-linux-gnu.
>
> Ok everywhere? (the testcase only fails on trunk)
>
> 2012-02-28 Richard Guenther
>
> PR target/52407
> * co
This fixes element ordering for V2SFmode, V2SImode and V2DImode
concats in ix86_expand_vector_set.
Boostrap / regtest pending on x86_64-unknown-linux-gnu.
Ok everywhere? (the testcase only fails on trunk)
Thanks,
Richard.
2012-02-28 Richard Guenther
PR target/52407
* confi