There are no clang or llvm* tests for EABI and no EABI buildbots.
*There is a single backend test that specifies EABI but it tests MIPS16.
Depends on D20678
Differential D20679
[mips] Kill 'support' for untested EABI. dsanders on May 26 2016, 7:10 AM. Authored by
Details There are no clang or llvm* tests for EABI and no EABI buildbots. *There is a single backend test that specifies EABI but it tests MIPS16. Depends on D20678
Diff Detail Event TimelineComment Actions LGTM Tools.cpp contains the following code. We need to remove eabi here too. if (CPUName.empty()) { // Deduce CPU name from ABI name. CPUName = llvm::StringSwitch<const char *>(ABIName) .Cases("o32", "eabi", DefMips32CPU) .Cases("n32", "n64", DefMips64CPU) .Default(""); } Comment Actions Removed the 'eabi' from Tools.cpp this revealed three driver tests for passing Comment Actions Just to double-check: Do you still agree we should kill this now that the number of tests covering EABI-specific behaviour is non-zero? I think we should on the basis that we still have no backend tests and no buildbots. The only tests we have check that the driver passes -mabi=eabi to the assembler. |