This define_expand is unused. It has been there since the
aarch64 backend was upstreamed. I think it is there due to
a misunderstanding on how the mov<mode>cc patterns where the
comparison is unrelated to the mode at hand.
I had noticed this while adding TImode comparison support since
we need to change the comparison code in some cases.
Bootstrapped and tested on aarch64-linux-gnu.
gcc/ChangeLog:
* config/aarch64/aarch64.md (mov<GPF:mode><GPI:mode>cc): Remove.
Signed-off-by: Andrew Pinski <[email protected]>
---
gcc/config/aarch64/aarch64.md | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
index 98c65a74c8e..b9ca4903893 100644
--- a/gcc/config/aarch64/aarch64.md
+++ b/gcc/config/aarch64/aarch64.md
@@ -4822,25 +4822,6 @@ (define_expand "mov<mode>cc"
}
)
-(define_expand "mov<GPF:mode><GPI:mode>cc"
- [(set (match_operand:GPI 0 "register_operand")
- (if_then_else:GPI (match_operand 1 "aarch64_comparison_operator")
- (match_operand:GPF 2 "register_operand")
- (match_operand:GPF 3 "register_operand")))]
- ""
- {
- rtx ccreg;
- enum rtx_code code = GET_CODE (operands[1]);
-
- if (code == UNEQ || code == LTGT)
- FAIL;
-
- ccreg = aarch64_gen_compare_reg (code, XEXP (operands[1], 0),
- XEXP (operands[1], 1));
- operands[1] = gen_rtx_fmt_ee (code, VOIDmode, ccreg, const0_rtx);
- }
-)
-
(define_expand "mov<mode>cc"
[(set (match_operand:GPF 0 "register_operand")
(if_then_else:GPF (match_operand 1 "aarch64_comparison_operator")
--
2.43.0
