On Wed, Jul 10, 2019 at 11:07 AM Richard Sandiford
wrote:
>
> Christophe Lyon writes:
> > On Mon, 8 Jul 2019 at 11:04, Richard Sandiford
> > wrote:
> >>
> >> Christophe Lyon writes:
> >> > Hi,
> >> >
> >> > This patch fixes PR 91060 where the lane ordering was no longer the
> >> > right one (GC
Christophe Lyon writes:
> On Mon, 8 Jul 2019 at 11:04, Richard Sandiford
> wrote:
>>
>> Christophe Lyon writes:
>> > Hi,
>> >
>> > This patch fixes PR 91060 where the lane ordering was no longer the
>> > right one (GCC's vs architecture's).
>>
>> Sorry, we clashed :-)
>>
>> I'd prefer to go with
On Mon, 8 Jul 2019 at 11:06, Kyrill Tkachov wrote:
>
> Hi Christophe
>
> On 7/8/19 10:01 AM, Christophe Lyon wrote:
> > Hi,
> >
> > This patch fixes PR 91060 where the lane ordering was no longer the
> > right one (GCC's vs architecture's).
> >
> > OK?
> >
> > Thanks to both Richards for most of t
On Mon, 8 Jul 2019 at 11:04, Richard Sandiford
wrote:
>
> Christophe Lyon writes:
> > Hi,
> >
> > This patch fixes PR 91060 where the lane ordering was no longer the
> > right one (GCC's vs architecture's).
>
> Sorry, we clashed :-)
>
> I'd prefer to go with the version I attached to bugzilla jus
Hi Christophe
On 7/8/19 10:01 AM, Christophe Lyon wrote:
Hi,
This patch fixes PR 91060 where the lane ordering was no longer the
right one (GCC's vs architecture's).
OK?
Thanks to both Richards for most of the debugging!
Thank you to all for tracking this down.
Christophe
pr91060.patc
Christophe Lyon writes:
> Hi,
>
> This patch fixes PR 91060 where the lane ordering was no longer the
> right one (GCC's vs architecture's).
Sorry, we clashed :-)
I'd prefer to go with the version I attached to bugzilla just now.
Thanks,
Richard
Hi,
This patch fixes PR 91060 where the lane ordering was no longer the
right one (GCC's vs architecture's).
OK?
Thanks to both Richards for most of the debugging!
Christophe
gcc/ChangeLog:
2019-07-08 Christophe Lyon
PR target/91060
* config/arm/arm.c (neon_expand_vector_in
