From: Michael LIAO <michael.hliao@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: autoconf@gnu.org, gcc@gcc.gnu.org, x32-abi@googlegroups.com,
config-patches@gnu.org
Subject: Re: new triplet for x32 psABI?
Date: Wed, 12 Oct 2011 04:49:00 -0000 [thread overview]
Message-ID: <CAO-CJbjBGnOSBegxizavKTjAWRJAJNbvae2pXZmThhbGHaHjjQ@mail.gmail.com> (raw)
In-Reply-To: <201110031834.35051.vapier@gentoo.org>
On Mon, Oct 3, 2011 at 3:34 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Monday, October 03, 2011 18:25:46 Michael LIAO wrote:
>> As x32 psABI (https://sites.google.com/site/x32abi/) is invented, do
>> we need a new triplet for system relies on triplet to figure out it's
>> targeted on x32 environment. The new triplet would look like
>> 'x86_64-unknown-linux-gnux32' for x32 vs 'x86_64-unknown-linux-gnu'
>> for regular 64-bit. This's similar to EABI added to ARM or PowerPC,
>> where 'arm-unknown-linux-gnueabi' vs. 'arm-unknown-linux-gnu'.
>
> do you have examples of why you need this ?
>
>> The current scheme documented on website
>> (https://sites.google.com/site/x32abi/) uses the existing triplet but
>> specify x32 ABI through compiler/linker options. It works for most
>> compilers aware of that, but how other tools not handling
>> compiler/linker options knows the current build is targeted on a
>> different environment?
>
> the mips people have been using a single tuple for multiple abis (n32 and
> n64), and it doesn't appear to have been a blocker for them ...
That's not true, at least to build glibc, you can use
'mips64-linux-gnuabi64' to specify a n64 build and
''mips64-linux-gnuabin32' for a n32 build without specifying compiler
option explicitly. I just figured this out from mips ports of glibc
from http://repo.or.cz/w/glibc-ports.git/blob/HEAD:/sysdeps/mips/preconfigure,
where both compiler option and triplet are checked and triplet is
preferred if they are not match.
> -mike
>
next prev parent reply other threads:[~2011-10-12 2:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 22:26 Michael LIAO
2011-10-03 22:30 ` Eric Blake
2011-10-03 22:35 ` Mike Frysinger
2011-10-03 22:57 ` Michael LIAO
2011-10-03 23:04 ` Mike Frysinger
2011-10-03 23:48 ` Michael LIAO
2011-10-04 0:47 ` Mike Frysinger
2011-10-04 3:26 ` Michael LIAO
2011-10-04 3:56 ` Mike Frysinger
2011-10-04 0:54 ` H.J. Lu
2011-10-04 3:44 ` Michael LIAO
2011-10-04 19:53 ` H.J. Lu
2011-10-03 23:06 ` H.J. Lu
2011-10-12 4:49 ` Michael LIAO [this message]
2011-10-12 7:13 ` Mike Frysinger
2011-10-12 7:27 ` Michael LIAO
2011-10-12 22:14 ` Mike Frysinger
2011-10-13 0:49 ` H.J. Lu
2011-10-13 7:26 ` 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=CAO-CJbjBGnOSBegxizavKTjAWRJAJNbvae2pXZmThhbGHaHjjQ@mail.gmail.com \
--to=michael.hliao@gmail.com \
--cc=autoconf@gnu.org \
--cc=config-patches@gnu.org \
--cc=gcc@gcc.gnu.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).