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'.
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 _______________________________________________ Autoconf mailing list [email protected] https://lists.gnu.org/mailman/listinfo/autoconf
