From: Richard Henderson <rth@twiddle.net>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
libc-alpha@sourceware.org, GCC Development <gcc@gcc.gnu.org>,
LKML <linux-kernel@vger.kernel.org>,
x32-abi@googlegroups.com
Subject: Re: X32 psABI status update
Date: Thu, 17 Mar 2011 10:38:41 -0700 [thread overview]
Message-ID: <4D824721.4020709@twiddle.net> (raw)
In-Reply-To: <AANLkTikfiVvxrxakH-_pch6v0jkT1yZstw4kXShyx+Sd@mail.gmail.com>
On 03/16/2011 10:21 PM, H.J. Lu wrote:
> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger <vapier@gentoo.org> 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~
next prev parent reply other threads:[~2011-03-17 17:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 19:08 X32 psABI status update H.J. Lu
2011-03-06 17:28 ` H.J. Lu
2011-03-07 21:33 ` Mike Frysinger
2011-03-16 4:17 ` H.J. Lu
2011-03-16 4:30 ` Mike Frysinger
2011-03-16 4:51 ` H.J. Lu
2011-03-16 5:24 ` Mike Frysinger
2011-03-16 12:39 ` H.J. Lu
2011-03-17 2:57 ` Mike Frysinger
2011-03-17 5:21 ` H.J. Lu
2011-03-17 5:45 ` Mike Frysinger
2011-03-17 14:43 ` H.J. Lu
2011-03-17 17:38 ` Richard Henderson [this message]
2011-03-21 5:08 ` Mike Frysinger
2011-03-21 5:35 ` H.J. Lu
2011-03-21 5:53 ` Mike Frysinger
2011-03-21 6:54 ` H.J. Lu
2011-03-21 8:20 ` Michael Matz
2011-03-21 10:52 ` H.J. Lu
[not found] ` <201103160124.42939.vapier__14164.6524928094$1300277836$gmane$org@gentoo.org>
2011-03-16 12:39 ` Andreas Schwab
2011-03-16 4:19 ` H.J. Lu
2011-03-17 8:46 ` X32 syscall number base Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D824721.4020709@twiddle.net \
--to=rth@twiddle.net \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.org \
--cc=x32-abi@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.