This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: ARM: non-NEON ARMv7 support broken?
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- Cc: <guillaume dot gardet at free dot fr>, <libc-ports at sourceware dot org>
- Date: Mon, 25 Nov 2013 18:15:05 +0000
- Subject: Re: ARM: non-NEON ARMv7 support broken?
- Authentication-results: sourceware.org; auth=none
- References: <529325AC dot 2020406 at free dot fr> <CAAHN_R12Gaj-TGut9EuRPaW9eeXwuz9tbmK5SgUqJsyotAfV-A at mail dot gmail dot com>
On Mon, 25 Nov 2013, Siddhesh Poyarekar wrote:
> On 25 November 2013 15:55, Guillaume Gardet <guillaume.gardet@free.fr> 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
joseph@codesourcery.com