From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2455 invoked by alias); 16 Mar 2011 12:40:06 -0000 Received: (qmail 2446 invoked by uid 22791); 16 Mar 2011 12:40:05 -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-iw0-f175.google.com (HELO mail-iw0-f175.google.com) (209.85.214.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 16 Mar 2011 12:40:00 +0000 Received: by iwn10 with SMTP id 10so1666768iwn.20 for ; Wed, 16 Mar 2011 05:39:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.141.196 with SMTP id p4mr904558icu.180.1300279197650; Wed, 16 Mar 2011 05:39:57 -0700 (PDT) Received: by 10.43.135.9 with HTTP; Wed, 16 Mar 2011 05:39:57 -0700 (PDT) In-Reply-To: <201103160124.42939.vapier@gentoo.org> References: <201103160030.27594.vapier@gentoo.org> <201103160124.42939.vapier@gentoo.org> Date: Wed, 16 Mar 2011 12:40:00 -0000 Message-ID: Subject: Re: X32 psABI status update From: "H.J. Lu" To: Mike Frysinger Cc: libc-alpha@sourceware.org, GCC Development , LKML , x32-abi@googlegroups.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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/msg00207.txt.bz2 On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger wrote: > On Wednesday, March 16, 2011 00:51:37 H.J. Lu wrote: >> On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger wrot= e: >> > On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote: >> >> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote: >> >> > On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote: >> >> >> Many x32 bugs are fixed in kernel, glibc, binutils and GCC: >> >> >> >> >> >> https://sites.google.com/site/x32abi/ >> >> >> >> >> >> The major remaining issues are glibc/gcc testsuite failures, >> >> >> kernel core dump and signal handler unwind. >> >> > >> >> > are you getting a unique host tuple for this ? =A0or are you extend= ing >> >> > x86_64- linux-gnu ? =A0so the only way of knowing which ABI is to c= heck >> >> > for the output of the compiler+compiler flags ? >> >> >> >> x32 requires x32 enabled x86-64 kernel. >> > >> > ok, but that doesnt answer my question. =A0what are you passing to --t= arget >> > ? >> >> See: >> >> https://sites.google.com/site/x32abi/ >> >> You configure it as >> >> CC=3D"gcc -mx32" ...../configure x86_64- linux-gnu > > that isnt what the page says. =A0it does say for glibc to do: > =A0 =A0 =A0 =A0CC=3D"x32-gcc -mx32 " CXX=3D"x32-g++ -mx32 " CFLAGS=3D"-O2= -g" =A0../configure > > but it doesnt say what to do for binutils or gcc itself. =A0obviously you= cant > use the -mx32 flag when building the cross gcc for the first time since t= he > current native gcc wont support it. > > the invocation given for glibc implies that the proposed tuple is x32-lin= ux- > gnu, but the GNU config project doesnt support that tuple and i didnt see > mention of it in the binutils or gcc sources. > > so we get back to my original e-mail: > =A0 =A0 =A0 =A0are you getting a unique host tuple for this ? =A0or are y= ou extending > =A0 =A0 =A0 =A0x86_64-linux-gnu ? =A0so the only way of knowing which ABI= is to check for > =A0 =A0 =A0 =A0the 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. --=20 H.J.