diff options
| author | Matt Arsenault <Matthew.Arsenault@amd.com> | 2025-08-05 18:23:36 +0900 |
|---|---|---|
| committer | Matt Arsenault <arsenm2@gmail.com> | 2025-08-05 18:37:06 +0900 |
| commit | 0cddf803a3250f8b1589fb73bfcee65e9b8d6559 (patch) | |
| tree | 2717535322dfa04f7dd79682dd430f185277274c | |
| parent | d1b363e0b0d1cce3aa24d998058144295237fa56 (diff) | |
ARM: Remove check for isAAPCS_ABI when enabling various aeabi callsusers/arsenm/arm/remove-check-is-aapcs-abi-aeabi-calls
Based on computeDefaultTargetABI, this appears to be redundant.
The only test using the explicit -target-abi flag with a value different
than one implied by the triple (i.e. assert(TM.isAAPCS_ABI()) under
the condition) is arm-abi-attr.ll and it doesn't stress the libcalls
used.
| -rw-r--r-- | llvm/lib/Target/ARM/ARMISelLowering.cpp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/lib/Target/ARM/ARMISelLowering.cpp b/llvm/lib/Target/ARM/ARMISelLowering.cpp index 7f8b4460bb81..a621e5c63eb0 100644 --- a/llvm/lib/Target/ARM/ARMISelLowering.cpp +++ b/llvm/lib/Target/ARM/ARMISelLowering.cpp @@ -588,8 +588,8 @@ ARMTargetLowering::ARMTargetLowering(const TargetMachine &TM_, } // RTLIB - if (TM.isAAPCS_ABI() && (TT.isTargetAEABI() || TT.isTargetGNUAEABI() || - TT.isTargetMuslAEABI() || TT.isAndroid())) { + if (TT.isTargetAEABI() || TT.isTargetGNUAEABI() || TT.isTargetMuslAEABI() || + TT.isAndroid()) { // FIXME: This does not depend on the subtarget and should go directly into // RuntimeLibcalls. This is only here because of missing support for setting // the calling convention of an implementation. |