From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 966 invoked by alias); 25 Nov 2013 10:26:04 -0000 Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org Received: (qmail 952 invoked by uid 89); 25 Nov 2013 10:26:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=BAYES_20,FREEMAIL_FROM,RDNS_NONE autolearn=no version=3.3.2 X-HELO: smtp1-g21.free.fr Received: from Unknown (HELO smtp1-g21.free.fr) (212.27.42.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 25 Nov 2013 10:26:03 +0000 Received: from [192.168.0.13] (unknown [82.244.147.214]) by smtp1-g21.free.fr (Postfix) with ESMTP id 8E1F79400B2 for ; Mon, 25 Nov 2013 11:25:49 +0100 (CET) Message-ID: <529325AC.2020406@free.fr> Date: Mon, 25 Nov 2013 10:29:00 -0000 From: Guillaume Gardet Reply-To: guillaume.gardet@free.fr User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: libc-ports@sourceware.org Subject: ARM: non-NEON ARMv7 support broken? OpenPGP: url=http://guillaume.gardet.free.fr/GPG/ClefGPGGuillaumeGardet.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-11/txt/msg00048.txt.bz2 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