[Patch][ARM] backport r266665 to gcc8

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Patch][ARM] backport r266665 to gcc8

Christophe Lyon-2
Hi,

Is it OK to backport r266665 to gcc8 (Ensure dotproduct is only
enabled on armv8 neon) ?
I've noticed unnecessary failure of gcc.target/arm/simd/vdot-compile.c
after I upgraded to recent binutils.

Thanks,

Christophe

dotprod.gcc8.chlog.txt (678 bytes) Download Attachment
dotprod.gcc8.patch.txt (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Patch][ARM] backport r266665 to gcc8

Richard Earnshaw (lists)
On 14/11/2019 08:40, Christophe Lyon wrote:

> Hi,
>
> Is it OK to backport r266665 to gcc8 (Ensure dotproduct is only
> enabled on armv8 neon) ?
> I've noticed unnecessary failure of gcc.target/arm/simd/vdot-compile.c
> after I upgraded to recent binutils.
>
> Thanks,
>
> Christophe
>

Is there a PR for this?

R.
Reply | Threaded
Open this post in threaded view
|

Re: [Patch][ARM] backport r266665 to gcc8

Christophe Lyon-2
On Fri, 15 Nov 2019 at 15:27, Richard Earnshaw (lists)
<[hidden email]> wrote:

>
> On 14/11/2019 08:40, Christophe Lyon wrote:
> > Hi,
> >
> > Is it OK to backport r266665 to gcc8 (Ensure dotproduct is only
> > enabled on armv8 neon) ?
> > I've noticed unnecessary failure of gcc.target/arm/simd/vdot-compile.c
> > after I upgraded to recent binutils.
> >
> > Thanks,
> >
> > Christophe
> >
>
> Is there a PR for this?
>

I don't think so, I couldn't find one. Maybe Sam remembers?


> R.