From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15254 invoked by alias); 12 Oct 2011 04:21:22 -0000 Received: (qmail 15242 invoked by uid 22791); 12 Oct 2011 04:21:19 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Oct 2011 04:21:02 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 0AE571B400B; Wed, 12 Oct 2011 04:21:01 +0000 (UTC) From: Mike Frysinger To: Michael LIAO Subject: Re: new triplet for x32 psABI? Date: Wed, 12 Oct 2011 07:13:00 -0000 User-Agent: KMail/1.13.7 (Linux/3.1.0-rc4; KDE/4.6.5; x86_64; ; ) Cc: autoconf@gnu.org, gcc@gcc.gnu.org, x32-abi@googlegroups.com, config-patches@gnu.org References: <201110031834.35051.vapier@gentoo.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1343866.QU4lGGRIJt"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201110120021.02469.vapier@gentoo.org> Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg00185.txt.bz2 --nextPart1343866.QU4lGGRIJt Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-length: 1500 On Tuesday 11 October 2011 22:55:35 Michael LIAO wrote: > On Mon, Oct 3, 2011 at 3:34 PM, Mike Frysinger wrote: > > On Monday, October 03, 2011 18:25:46 Michael LIAO wrote: > >> The current scheme documented on website > >> (https://sites.google.com/site/x32abi/) uses the existing triplet but > >> specify x32 ABI through compiler/linker options. It works for most > >> compilers aware of that, but how other tools not handling > >> compiler/linker options knows the current build is targeted on a > >> different environment? > >=20 > > the mips people have been using a single tuple for multiple abis (n32 a= nd > > n64), and it doesn't appear to have been a blocker for them ... >=20 > That's not true, at least to build glibc, you can use > 'mips64-linux-gnuabi64' to specify a n64 build and > ''mips64-linux-gnuabin32' for a n32 build without specifying compiler > option explicitly. I just figured this out from mips ports of glibc > from > http://repo.or.cz/w/glibc-ports.git/blob/HEAD:/sysdeps/mips/preconfigure, > where both compiler option and triplet are checked and triplet is > preferred if they are not match. while it is true glibc has this code, it doesn't make my statements incorre= ct:=20 a single tuple works just fine with mips for multiple ABIs. if you look at= =20 other projects like gcc, it doesn't check this field at all. so you're sti= ll=20 right where you started: you still haven't shown any cases which necessitat= e a=20 dedicated tuple. -mike --nextPart1343866.QU4lGGRIJt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJOlRWuAAoJEEFjO5/oN/WBUzAP/j7NwRAVEkhV0q9O5CZydZy9 d0TnDCQfG9fyCt2ovRZtHN4O7zOfkW/VXv9zftWqEl1fNLL7IiapwCTwT7/feDaF Ys4+NyOtWZffXGPABtf4PKGc/Vvyw/RRRGmOR50osh45rM/2qEWiyJsV75YPqiya xQtJm9r14moRhjhXnTZD3FO0pTiH8ZjfEA9wZclS7dcVzcr3ugwO0SxsgB3lewzJ cp+nHxK3FQ3dQs8Una2oZAyd8VjwrPXChaXUU5s+io6PKJ9cSyCQH7XpTk+bo93L jTd0apd+nu9RkYKyWjxbM1xqSupZxsGlY3ih68EpaKBzT3kMnVRfowhR30Tue86u CjSV+pxrrxumrlqJKFUotYHTqKFs862J3UAEq+1FsksEsiUEVTyrgXAIwlKvmbD0 Nky6g6OV/NZNqwYGkq+ze4H2JXVgIH4Ru6FweBKn1eTQUrmSHCK3E7RdCuSl5kPx OaRven+K7z3EnSZ3oosQiptIyxWpAogBBPn3Jwko5KN6/KUidv7FTRQ5bb1ZvCQ1 Tb7GLQCT52J8nBW0RGK7bA8cJZCuZEpOUeDWQrWGM+jpwVFTNNQBjHpzwb7PfgsS dw8WEZLQ17ClKHxsCFrzqzlG7fbXeCQ+RjQd1ntuBP94Vv+KMFBRIMo7G9qiQyTn M0BAl80/RrrLALhE+jdF =C3B4 -----END PGP SIGNATURE----- --nextPart1343866.QU4lGGRIJt--