From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30684 invoked by alias); 3 Oct 2011 22:26:08 -0000 Received: (qmail 30675 invoked by uid 22791); 3 Oct 2011 22:26:06 -0000 X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL 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; Mon, 03 Oct 2011 22:25:47 +0000 Received: by wyh5 with SMTP id 5so4125044wyh.20 for ; Mon, 03 Oct 2011 15:25:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.188.65 with SMTP id z43mr609845wem.15.1317680746148; Mon, 03 Oct 2011 15:25:46 -0700 (PDT) Received: by 10.216.168.10 with HTTP; Mon, 3 Oct 2011 15:25:46 -0700 (PDT) Date: Mon, 03 Oct 2011 22:26:00 -0000 Message-ID: Subject: new triplet for x32 psABI? From: Michael LIAO To: autoconf@gnu.org, gcc@gcc.gnu.org, x32-abi@googlegroups.com 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/msg00022.txt.bz2 Sorry, resend with plain text format. Hi, Everyone 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'. The new triple doesn't introduce a new target (still x86_64) but just a new environment 'gnux32' to specify x32 ABI is used for code generation. 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? Any comments or alternative suggestion? Yours - Michael