rs6000: fix misleading new patterns of splitters
As a comment in https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599556.html Those splitters call rs6000_emit_set_const directly, and the replacements are never used. Using (pc) would be less misleading. gcc/ChangeLog: * config/rs6000/rs6000.md: (constant splitters): Use "(pc)" as the replacements.
This commit is contained in:
parent
c0852b51b7
commit
34ea461fdb
1 changed files with 3 additions and 9 deletions
|
@ -7773,11 +7773,7 @@
|
|||
[(set (match_operand:SI 0 "gpc_reg_operand")
|
||||
(match_operand:SI 1 "const_int_operand"))]
|
||||
"num_insns_constant (operands[1], SImode) > 1"
|
||||
[(set (match_dup 0)
|
||||
(match_dup 2))
|
||||
(set (match_dup 0)
|
||||
(ior:SI (match_dup 0)
|
||||
(match_dup 3)))]
|
||||
[(pc)]
|
||||
{
|
||||
if (rs6000_emit_set_const (operands[0], operands[1]))
|
||||
DONE;
|
||||
|
@ -9708,8 +9704,7 @@
|
|||
[(set (match_operand:DI 0 "int_reg_operand_not_pseudo")
|
||||
(match_operand:DI 1 "const_int_operand"))]
|
||||
"TARGET_POWERPC64 && num_insns_constant (operands[1], DImode) > 1"
|
||||
[(set (match_dup 0) (match_dup 2))
|
||||
(set (match_dup 0) (plus:DI (match_dup 0) (match_dup 3)))]
|
||||
[(pc)]
|
||||
{
|
||||
if (rs6000_emit_set_const (operands[0], operands[1]))
|
||||
DONE;
|
||||
|
@ -9721,8 +9716,7 @@
|
|||
[(set (match_operand:DI 0 "int_reg_operand_not_pseudo")
|
||||
(match_operand:DI 1 "const_scalar_int_operand"))]
|
||||
"TARGET_POWERPC64 && num_insns_constant (operands[1], DImode) > 1"
|
||||
[(set (match_dup 0) (match_dup 2))
|
||||
(set (match_dup 0) (plus:DI (match_dup 0) (match_dup 3)))]
|
||||
[(pc)]
|
||||
{
|
||||
if (rs6000_emit_set_const (operands[0], operands[1]))
|
||||
DONE;
|
||||
|
|
Loading…
Add table
Reference in a new issue