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 ... -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
