From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4368 invoked by alias); 17 Mar 2011 17:38:51 -0000 Received: (qmail 4340 invoked by uid 22791); 17 Mar 2011 17:38:49 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from b.mail.sonic.net (HELO b.mail.sonic.net) (64.142.19.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 Mar 2011 17:38:44 +0000 Received: from are.twiddle.net (are.twiddle.net [75.101.38.216]) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p2HHcgmh021375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2011 10:38:43 -0700 Received: from anchor.twiddle.home (anchor.twiddle.home [172.31.0.4]) by are.twiddle.net (8.14.4/8.14.4) with ESMTP id p2HHcfjl030198; Thu, 17 Mar 2011 10:38:41 -0700 Message-ID: <4D824721.4020709@twiddle.net> Date: Thu, 17 Mar 2011 17:38:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 MIME-Version: 1.0 To: "H.J. Lu" CC: Mike Frysinger , libc-alpha@sourceware.org, GCC Development , LKML , x32-abi@googlegroups.com Subject: Re: X32 psABI status update References: <201103160124.42939.vapier@gentoo.org> <201103162257.10440.vapier@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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-03/txt/msg00229.txt.bz2 On 03/16/2011 10:21 PM, H.J. Lu wrote: > On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote: >> On Wednesday, March 16, 2011 08:39:57 H.J. Lu wrote: >>> On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger wrote: >>>> so we get back to my original e-mail: >>>> are you getting a unique host tuple for this ? or are you >>>> extending x86_64-linux-gnu ? so the only way of knowing which ABI is to >>>> check for the output of the compiler+compiler flags ? >>> >>> As I said, the target is x86_64- linux-gnu and you just add -mx32 to >>> CFLAGS. The x86_64- linux-gnu binutils and GCC support x32. >> >> ok, took long enough, but that answers most things. your usage of "x32-" >> prefixed binaries in the documentation seems to imply a lot more than the fact >> you just picked those locally to avoid system collisions. this isnt a wiki >> page, otherwise i'd clean things up for you. > > Any suggestion how to create a wiki page for x32? Hanging it off of gcc.gnu.org/wiki wouldn't be a bad idea, imo. r~