On Mon, Oct 3, 2011 at 3:57 PM, Michael LIAO <michael.hliao@xxxxxxxxx> wrote: > Most examples would be related to tools generating code. > > Suppose you have a software package with several hard-coded fully > optimized assembly file for different targets. Your build system need > to know the current target as well as target ABI to select the correct > assembly file to build it. It even desirable if it includes a simple > script to help generate assembly code (like the one in OpenSSL), you'd > better know the target ABI to prepare proper glue code without > breaking ABI. > X32 assembly codes are very close to x86-64 ones. In come cases, they are 100% compatible. In kernel, x32 vDSO is built from the x86-64 .o files for x86-64 vDSO. In gmp, you can assemble x86-64 assembly codes directly into x32 object files. Adding x32 target triplet may not be necessarily helpful. -- H.J. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
