On 10/03/2011 04:25 PM, Michael LIAO wrote:
Sorry, resend with plain text format.
Hi, Everyone
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'.
Discussions on new triplets are worthless on the autoconf list, which is
only a downstream consumer of config.guess; rather, your questions
should be directed to config-patc...@gnu.org [added to cc].
The new triple doesn't introduce a new target (still x86_64) but just
a new environment 'gnux32' to specify x32 ABI is used for code
generation.
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?
Any comments or alternative suggestion?
Yours
- Michael
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
