From: Andreas Schwab <schwab@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
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 13:39:57 +0100 [thread overview]
Message-ID: <m3ipvjs0gy.fsf@redhat.com> (raw)
In-Reply-To: <201103160124.42939.vapier__14164.6524928094$1300277836$gmane$org@gentoo.org> (Mike Frysinger's message of "Wed, 16 Mar 2011 01:24:41 -0400")
Mike Frysinger <vapier@gentoo.org> writes:
> 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.
Of course, for a compiler tool the only thing that matters is the
target.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next prev parent reply other threads:[~2011-03-16 12:40 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
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 [this message]
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=m3ipvjs0gy.fsf@redhat.com \
--to=schwab@redhat.com \
--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.