Displaying 2 results from an estimated 2 matches for "abitriple".
2016 Jun 24
7
Representing MIPS ABI information in the triple as ARM/X86 do for EABI/EABIHF/X32
...this point, you may be wondering what happens to Triple::GNU for triples like mips-linux-gnu and mips64-linux-gnu. The answer to this is that the API-user (e.g. clang) is expected to normalize such triples down to one of Triple::GNUABI32/GNUABIN32/GNUABI64. This can be as simple as adding:
Triple ABITriple = TT.getABIVariant(ABIName); // ABIName can be the empty string to get the default ABI.
if (ABITriple.getArch() != Triple::UnknownArch) {
TT = ABITriple;
ABIName = ""; // <- Only needed if this would end up in MCTargetOptions::ABIName.
}
to the appropriate place in the call...
2016 Jul 05
2
Representing MIPS ABI information in the triple as ARM/X86 do for EABI/EABIHF/X32
...this point, you may be wondering what happens to Triple::GNU for triples like mips-linux-gnu and mips64-linux-gnu. The answer to this is that the API-user (e.g. clang) is expected to normalize such triples down to one of Triple::GNUABI32/GNUABIN32/GNUABI64. This can be as simple as adding:
Triple ABITriple = TT.getABIVariant(ABIName); // ABIName can be the empty string to get the default ABI.
if (ABITriple.getArch() != Triple::UnknownArch) {
TT = ABITriple;
ABIName = ""; // <- Only needed if this would end up in MCTargetOptions::ABIName.
}
to the appropriate place in the call...