This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: new triplet for x32 psABI?
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
>