From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: 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: Wed, 16 Mar 2011 12:40:00 -0000 [thread overview]
Message-ID: <AANLkTim4w7zBBnsu+A1TMtb-wv60urDiSk5T0qbg7Oze@mail.gmail.com> (raw)
In-Reply-To: <201103160124.42939.vapier@gentoo.org>
On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Wednesday, March 16, 2011 00:51:37 H.J. Lu wrote:
>> On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> > 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 ? 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 ?
>> >>
>> >> x32 requires x32 enabled x86-64 kernel.
>> >
>> > ok, but that doesnt answer my question. what are you passing to --target
>> > ?
>>
>> See:
>>
>> https://sites.google.com/site/x32abi/
>>
>> You configure it as
>>
>> CC="gcc -mx32" ...../configure x86_64- linux-gnu
>
> that isnt what the page says. it does say for glibc to do:
> CC="x32-gcc -mx32 " CXX="x32-g++ -mx32 " CFLAGS="-O2 -g" ../configure
>
> but it doesnt say what to do for binutils or gcc itself. obviously you cant
> use the -mx32 flag when building the cross gcc for the first time since the
> current native gcc wont support it.
>
> the invocation given for glibc implies that the proposed tuple is x32-linux-
> 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:
> 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.
--
H.J.
next prev parent reply other threads:[~2011-03-16 12:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 19:08 H.J. Lu
2011-03-06 17:29 ` 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:40 ` H.J. Lu [this message]
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
2011-03-21 5:09 ` Mike Frysinger
2011-03-21 5:35 ` H.J. Lu
2011-03-21 5:53 ` Mike Frysinger
2011-03-21 6:55 ` 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:40 ` Andreas Schwab
2011-03-16 4:19 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 11:04 x32 " H.J. Lu
2011-02-19 20:57 ` H.J. Lu
2011-02-19 22:01 ` H.J. Lu
[not found] ` <AANLkTikkpK9ouXckHaVzwXe+p_Cz2hVH5T7xOoQL7OSE@mail.gmail.com>
2011-02-19 22:52 ` H.J. Lu
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=AANLkTim4w7zBBnsu+A1TMtb-wv60urDiSk5T0qbg7Oze@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc@gcc.gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).