From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4090 invoked by alias); 2 Aug 2012 17:28:59 -0000 Received: (qmail 4072 invoked by uid 22791); 2 Aug 2012 17:28:57 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from toast.topped-with-meat.com (HELO topped-with-meat.com) (204.197.218.159) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 02 Aug 2012 17:28:44 +0000 Received: by topped-with-meat.com (Postfix, from userid 5281) id AC5092C0DF; Thu, 2 Aug 2012 10:28:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Steve McIntyre Cc: libc-alpha@sourceware.org, libc-ports@sourceware.org Subject: Re: ARM hard-float ABI: add ldconfig flag value In-Reply-To: Steve McIntyre's message of Thursday, 2 August 2012 17:56:58 +0100 <20120802165658.GG24537@linaro.org> References: <20120727160941.GA13597@linaro.org> <20120802165658.GG24537@linaro.org> Message-Id: <20120802172843.AC5092C0DF@topped-with-meat.com> Date: Thu, 02 Aug 2012 17:28:00 -0000 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.0 cv=e8d9udV/ c=1 sm=1 a=uU3AHZwMbGkA:10 a=Z6MIti7PxpgA:10 a=kj9zAlcOel0A:10 a=hOe2yjtxAAAA:8 a=14OXPxybAAAA:8 a=CCpqsmhAAAAA:8 a=HukNdTy-7AoaRnY8p0MA:9 a=CjuIK1q_8ugA:10 a=4t78-hnhQh4A:10 a=WkljmVdYkabdwxfqvArNOQ==:117 X-IsSubscribed: yes 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 X-SW-Source: 2012-08/txt/msg00010.txt.bz2 libc-ports@sourceware.org is the right list for discussing ARM. OSABI is used in a generic way and should not be used for machine-specific purposes. An e_flags (EF_*) bit is probably a better choice. There are already these bits (among others): #define EF_ARM_SOFT_FLOAT 0x200 #define EF_ARM_VFP_FLOAT 0x400 #define EF_ARM_MAVERICK_FLOAT 0x800 But I don't know the history of their use. Off hand EF_ARM_VFP_FLOAT seems like it's already what you want, but maybe it has a different meaning (like just that it uses VFP, not that the ABI specifies using VFP registers in the calling convention). Thanks, Roland