-
Notifications
You must be signed in to change notification settings - Fork 13.6k
ARM: Stop using setCmpLibcallCC in MachO case #142710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
arsenm
wants to merge
1
commit into
main
Choose a base branch
from
users/arsenm/arm-remove-macho-use-setCmpLibcallCC
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
setCmpLibcallCC appears to be a hack to express a non 0/1 return value difference in the eabi case that's only relevant when expanding unordered compares. I see no test changes if I remove this case.
@llvm/pr-subscribers-backend-arm Author: Matt Arsenault (arsenm) ChangessetCmpLibcallCC appears to be a hack to express a non 0/1 return Full diff: https://github.com/llvm/llvm-project/pull/142710.diff 1 Files Affected:
diff --git a/llvm/lib/Target/ARM/ARMISelLowering.cpp b/llvm/lib/Target/ARM/ARMISelLowering.cpp
index d156851d7e214..5ba4bf03270bc 100644
--- a/llvm/lib/Target/ARM/ARMISelLowering.cpp
+++ b/llvm/lib/Target/ARM/ARMISelLowering.cpp
@@ -523,67 +523,65 @@ ARMTargetLowering::ARMTargetLowering(const TargetMachine &TM,
Subtarget->hasARMOps() && !Subtarget->useSoftFloat()) {
static const struct {
const RTLIB::Libcall Op;
- const char * const Name;
- const ISD::CondCode Cond;
+ const char *const Name;
} LibraryCalls[] = {
- // Single-precision floating-point arithmetic.
- { RTLIB::ADD_F32, "__addsf3vfp", ISD::SETCC_INVALID },
- { RTLIB::SUB_F32, "__subsf3vfp", ISD::SETCC_INVALID },
- { RTLIB::MUL_F32, "__mulsf3vfp", ISD::SETCC_INVALID },
- { RTLIB::DIV_F32, "__divsf3vfp", ISD::SETCC_INVALID },
-
- // Double-precision floating-point arithmetic.
- { RTLIB::ADD_F64, "__adddf3vfp", ISD::SETCC_INVALID },
- { RTLIB::SUB_F64, "__subdf3vfp", ISD::SETCC_INVALID },
- { RTLIB::MUL_F64, "__muldf3vfp", ISD::SETCC_INVALID },
- { RTLIB::DIV_F64, "__divdf3vfp", ISD::SETCC_INVALID },
-
- // Single-precision comparisons.
- { RTLIB::OEQ_F32, "__eqsf2vfp", ISD::SETNE },
- { RTLIB::UNE_F32, "__nesf2vfp", ISD::SETNE },
- { RTLIB::OLT_F32, "__ltsf2vfp", ISD::SETNE },
- { RTLIB::OLE_F32, "__lesf2vfp", ISD::SETNE },
- { RTLIB::OGE_F32, "__gesf2vfp", ISD::SETNE },
- { RTLIB::OGT_F32, "__gtsf2vfp", ISD::SETNE },
- { RTLIB::UO_F32, "__unordsf2vfp", ISD::SETNE },
-
- // Double-precision comparisons.
- { RTLIB::OEQ_F64, "__eqdf2vfp", ISD::SETNE },
- { RTLIB::UNE_F64, "__nedf2vfp", ISD::SETNE },
- { RTLIB::OLT_F64, "__ltdf2vfp", ISD::SETNE },
- { RTLIB::OLE_F64, "__ledf2vfp", ISD::SETNE },
- { RTLIB::OGE_F64, "__gedf2vfp", ISD::SETNE },
- { RTLIB::OGT_F64, "__gtdf2vfp", ISD::SETNE },
- { RTLIB::UO_F64, "__unorddf2vfp", ISD::SETNE },
-
- // Floating-point to integer conversions.
- // i64 conversions are done via library routines even when generating VFP
- // instructions, so use the same ones.
- { RTLIB::FPTOSINT_F64_I32, "__fixdfsivfp", ISD::SETCC_INVALID },
- { RTLIB::FPTOUINT_F64_I32, "__fixunsdfsivfp", ISD::SETCC_INVALID },
- { RTLIB::FPTOSINT_F32_I32, "__fixsfsivfp", ISD::SETCC_INVALID },
- { RTLIB::FPTOUINT_F32_I32, "__fixunssfsivfp", ISD::SETCC_INVALID },
-
- // Conversions between floating types.
- { RTLIB::FPROUND_F64_F32, "__truncdfsf2vfp", ISD::SETCC_INVALID },
- { RTLIB::FPEXT_F32_F64, "__extendsfdf2vfp", ISD::SETCC_INVALID },
-
- // Integer to floating-point conversions.
- // i64 conversions are done via library routines even when generating VFP
- // instructions, so use the same ones.
- // FIXME: There appears to be some naming inconsistency in ARM libgcc:
- // e.g., __floatunsidf vs. __floatunssidfvfp.
- { RTLIB::SINTTOFP_I32_F64, "__floatsidfvfp", ISD::SETCC_INVALID },
- { RTLIB::UINTTOFP_I32_F64, "__floatunssidfvfp", ISD::SETCC_INVALID },
- { RTLIB::SINTTOFP_I32_F32, "__floatsisfvfp", ISD::SETCC_INVALID },
- { RTLIB::UINTTOFP_I32_F32, "__floatunssisfvfp", ISD::SETCC_INVALID },
+ // Single-precision floating-point arithmetic.
+ {RTLIB::ADD_F32, "__addsf3vfp"},
+ {RTLIB::SUB_F32, "__subsf3vfp"},
+ {RTLIB::MUL_F32, "__mulsf3vfp"},
+ {RTLIB::DIV_F32, "__divsf3vfp"},
+
+ // Double-precision floating-point arithmetic.
+ {RTLIB::ADD_F64, "__adddf3vfp"},
+ {RTLIB::SUB_F64, "__subdf3vfp"},
+ {RTLIB::MUL_F64, "__muldf3vfp"},
+ {RTLIB::DIV_F64, "__divdf3vfp"},
+
+ // Single-precision comparisons.
+ {RTLIB::OEQ_F32, "__eqsf2vfp"},
+ {RTLIB::UNE_F32, "__nesf2vfp"},
+ {RTLIB::OLT_F32, "__ltsf2vfp"},
+ {RTLIB::OLE_F32, "__lesf2vfp"},
+ {RTLIB::OGE_F32, "__gesf2vfp"},
+ {RTLIB::OGT_F32, "__gtsf2vfp"},
+ {RTLIB::UO_F32, "__unordsf2vfp"},
+
+ // Double-precision comparisons.
+ {RTLIB::OEQ_F64, "__eqdf2vfp"},
+ {RTLIB::UNE_F64, "__nedf2vfp"},
+ {RTLIB::OLT_F64, "__ltdf2vfp"},
+ {RTLIB::OLE_F64, "__ledf2vfp"},
+ {RTLIB::OGE_F64, "__gedf2vfp"},
+ {RTLIB::OGT_F64, "__gtdf2vfp"},
+ {RTLIB::UO_F64, "__unorddf2vfp"},
+
+ // Floating-point to integer conversions.
+ // i64 conversions are done via library routines even when generating
+ // VFP
+ // instructions, so use the same ones.
+ {RTLIB::FPTOSINT_F64_I32, "__fixdfsivfp"},
+ {RTLIB::FPTOUINT_F64_I32, "__fixunsdfsivfp"},
+ {RTLIB::FPTOSINT_F32_I32, "__fixsfsivfp"},
+ {RTLIB::FPTOUINT_F32_I32, "__fixunssfsivfp"},
+
+ // Conversions between floating types.
+ {RTLIB::FPROUND_F64_F32, "__truncdfsf2vfp"},
+ {RTLIB::FPEXT_F32_F64, "__extendsfdf2vfp"},
+
+ // Integer to floating-point conversions.
+ // i64 conversions are done via library routines even when generating
+ // VFP
+ // instructions, so use the same ones.
+ // FIXME: There appears to be some naming inconsistency in ARM libgcc:
+ // e.g., __floatunsidf vs. __floatunssidfvfp.
+ {RTLIB::SINTTOFP_I32_F64, "__floatsidfvfp"},
+ {RTLIB::UINTTOFP_I32_F64, "__floatunssidfvfp"},
+ {RTLIB::SINTTOFP_I32_F32, "__floatsisfvfp"},
+ {RTLIB::UINTTOFP_I32_F32, "__floatunssisfvfp"},
};
- for (const auto &LC : LibraryCalls) {
+ for (const auto &LC : LibraryCalls)
setLibcallName(LC.Op, LC.Name);
- if (LC.Cond != ISD::SETCC_INVALID)
- setCmpLibcallCC(LC.Op, LC.Cond);
- }
}
}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
setCmpLibcallCC appears to be a hack to express a non 0/1 return
value difference in the eabi case that's only relevant when
expanding unordered compares. I see no test changes if I remove
this case.