public inbox for
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <>
Subject: Re: ARM: non-NEON ARMv7 support broken?
Date: Mon, 25 Nov 2013 10:32:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 25 November 2013 15:55, Guillaume Gardet <> 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:


  reply	other threads:[~2013-11-25 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 10:29 Guillaume Gardet
2013-11-25 10:32 ` Siddhesh Poyarekar [this message]
2013-11-25 18:15   ` Guillaume Gardet
2013-11-26  8:58   ` Joseph S. Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).