From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25273 invoked by alias); 12 Oct 2011 02:55:51 -0000 Received: (qmail 25265 invoked by uid 22791); 12 Oct 2011 02:55:51 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-wy0-f175.google.com (HELO mail-wy0-f175.google.com) (74.125.82.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Oct 2011 02:55:37 +0000 Received: by wyh5 with SMTP id 5so257139wyh.20 for ; Tue, 11 Oct 2011 19:55:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.229.38 with SMTP id g38mr8557398weq.36.1318388135564; Tue, 11 Oct 2011 19:55:35 -0700 (PDT) Received: by 10.216.25.206 with HTTP; Tue, 11 Oct 2011 19:55:35 -0700 (PDT) In-Reply-To: <201110031834.35051.vapier@gentoo.org> References: <201110031834.35051.vapier@gentoo.org> Date: Wed, 12 Oct 2011 04:49:00 -0000 Message-ID: Subject: Re: new triplet for x32 psABI? From: Michael LIAO To: Mike Frysinger Cc: autoconf@gnu.org, gcc@gcc.gnu.org, x32-abi@googlegroups.com, config-patches@gnu.org Content-Type: text/plain; charset=UTF-8 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/msg00183.txt.bz2 On Mon, Oct 3, 2011 at 3:34 PM, Mike Frysinger wrote: > On Monday, October 03, 2011 18:25:46 Michael LIAO wrote: >> As x32 psABI (https://sites.google.com/site/x32abi/) is invented, do >> we need a new triplet for system relies on triplet to figure out it's >> targeted on x32 environment. The new triplet would look like >> 'x86_64-unknown-linux-gnux32' for x32 vs 'x86_64-unknown-linux-gnu' >> for regular 64-bit. This's similar to EABI added to ARM or PowerPC, >> where 'arm-unknown-linux-gnueabi' vs. 'arm-unknown-linux-gnu'. > > do you have examples of why you need this ? > >> 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? > > the mips people have been using a single tuple for multiple abis (n32 and > n64), and it doesn't appear to have been a blocker for them ... 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. > -mike >