ARM: non-NEON ARMv7 support broken?

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

ARM: non-NEON ARMv7 support broken?

Guillaume Gardet
Hi,

we (openSUSE ARM team) have problems with glibc 2.18 on ARMv7 boards (Mirabox and Tegra 2 tablet) which are not NEON capable. We have no problem on Beagleboard xM or pandaboard wich have NEON capable SoC.

Apparently, NEON instructions are used in glibc and lead to invalid instruction errors.

Reverting to glibc 2.17 from previous openSUSE version fixes the problems.

Is there anything we missed between 2.17 and 2.18?

Should glibc detect NEON capable CPU at run time?


Guillaume

Reply | Threaded
Open this post in threaded view
|

Re: ARM: non-NEON ARMv7 support broken?

Siddhesh Poyarekar
On 25 November 2013 15:55, Guillaume Gardet <[hidden email]> wrote:

> Hi,
>
> we (openSUSE ARM team) have problems with glibc 2.18 on ARMv7 boards (Mirabox and Tegra 2 tablet) which are not NEON capable. We have no problem on Beagleboard xM or pandaboard wich have NEON capable SoC.
>
> Apparently, NEON instructions are used in glibc and lead to invalid instruction errors.
>
> Reverting to glibc 2.17 from previous openSUSE version fixes the problems.
>
> Is there anything we missed between 2.17 and 2.18?
>
> Should glibc detect NEON capable CPU at run time?

That sounds like:

https://sourceware.org/bugzilla/show_bug.cgi?id=15905

Siddhesh
--
http://siddhesh.in
Reply | Threaded
Open this post in threaded view
|

Re: ARM: non-NEON ARMv7 support broken?

Guillaume Gardet

Le 25/11/2013 11:29, Siddhesh Poyarekar a écrit :

> On 25 November 2013 15:55, Guillaume Gardet <[hidden email]> wrote:
>> Hi,
>>
>> we (openSUSE ARM team) have problems with glibc 2.18 on ARMv7 boards (Mirabox and Tegra 2 tablet) which are not NEON capable. We have no problem on Beagleboard xM or pandaboard wich have NEON capable SoC.
>>
>> Apparently, NEON instructions are used in glibc and lead to invalid instruction errors.
>>
>> Reverting to glibc 2.17 from previous openSUSE version fixes the problems.
>>
>> Is there anything we missed between 2.17 and 2.18?
>>
>> Should glibc detect NEON capable CPU at run time?
> That sounds like:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=15905

Thanks a lot!

Will try this patch.


Guillaume

>
> Siddhesh

Reply | Threaded
Open this post in threaded view
|

Re: ARM: non-NEON ARMv7 support broken?

Joseph Myers
In reply to this post by Siddhesh Poyarekar
On Mon, 25 Nov 2013, Siddhesh Poyarekar wrote:

> On 25 November 2013 15:55, Guillaume Gardet <[hidden email]> wrote:
> > Hi,
> >
> > we (openSUSE ARM team) have problems with glibc 2.18 on ARMv7 boards (Mirabox and Tegra 2 tablet) which are not NEON capable. We have no problem on Beagleboard xM or pandaboard wich have NEON capable SoC.
> >
> > Apparently, NEON instructions are used in glibc and lead to invalid instruction errors.
> >
> > Reverting to glibc 2.17 from previous openSUSE version fixes the problems.
> >
> > Is there anything we missed between 2.17 and 2.18?
> >
> > Should glibc detect NEON capable CPU at run time?
>
> That sounds like:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=15905

I noted in <https://sourceware.org/ml/libc-ports/2013-08/msg00066.html>
that this fix seemed appropriate for 2.18 branch, but it looks like it
didn't get pushed there.

--
Joseph S. Myers
[hidden email]