search for: why_not_use_gnu_triplet

...given the right options. The main issue I have at the moment is with the N32 and N64 ABI's. These are ILP32 and LP64 respectively, are mutually incompatible, and have traditionally used the same triple. There's an ARM example of the same problem at https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F. In that example, hard-float and soft-float both used arm-linux-gnueabi but were mutually incompatible. The Multiarch tuples described on that page are an attempt to resolve the ambiguity but I'm told that they aren't likely to be universally adopted. Maybe, a better solution is to hav...

...e recent versions. On a similar > note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical > MIPS32 implementations) rather than the usual MIPS-I. The last example of > this ambiguity I'd like to reference is that mentioned by > https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F. In > that example, hard-float and soft-float on ARM both used arm-linux-gnueabi > but were mutually incompatible. The Multiarch tuples described on that page > are an attempt to resolve the ambiguity but I'm told that they aren't > likely to be universally adopted. > &gt...

...ut means i586 on more recent versions. On a similar note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical MIPS32 implementations) rather than the usual MIPS-I. The last example of this ambiguity I'd like to reference is that mentioned by https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F. In that example, hard-float and soft-float on ARM both used arm-linux-gnueabi but were mutually incompatible. The Multiarch tuples described on that page are an attempt to resolve the ambiguity but I'm told that they aren't likely to be universally adopted. The third reason, is that d...

Hi, I've been having trouble properly resolving an issue with our assembly syntax. The prefix our assembler uses for private local/global labels depends on the object file format. For ELF32 they begin with '$' and for ELF64 they begin with '.L'. The object file format depends on the ABI, but multiple ABI's are usable with the same target triple so we can't select

...ut means i586 on more recent versions. On a similar note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical MIPS32 implementations) rather than the usual MIPS-I. The last example of this ambiguity I'd like to reference is that mentioned by https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F. In that example, hard-float and soft-float on ARM both used arm-linux-gnueabi but were mutually incompatible. The Multiarch tuples described on that page are an attempt to resolve the ambiguity but I'm told that they aren't likely to be universally adopted. The third reason, is that d...

...e recent versions. On a similar > note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical > MIPS32 implementations) rather than the usual MIPS-I. The last example of > this ambiguity I'd like to reference is that mentioned by > https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F. In > that example, hard-float and soft-float on ARM both used arm-linux-gnueabi > but were mutually incompatible. The Multiarch tuples described on that page > are an attempt to resolve the ambiguity but I'm told that they aren't > likely to be universally adopted. > &gt...

...ut means i586 on more recent versions. On a similar note, on Debian, mips-linux-gnu targets MIPS-II (optimised for typical MIPS32 implementations) rather than the usual MIPS-I. The last example of this ambiguity I'd like to reference is that mentioned by https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F. In that example, hard-float and soft-float on ARM both used arm-linux-gnueabi but were mutually incompatible. The Multiarch tuples described on that page are an attempt to resolve the ambiguity but I'm told that they aren't likely to be universally adopted. The third reason, is that d...