diff options
| author | Andreas Schwab <schwab@suse.de> | 2024-11-21 15:35:01 +0100 |
|---|---|---|
| committer | Andreas Schwab <schwab@suse.de> | 2024-12-02 16:51:37 +0100 |
| commit | cec97549b781643f55bde34d025c3170309e3646 (patch) | |
| tree | c313d33aed26548a14e4dcd9c88f4fe1cbd5b25b /gcc | |
| parent | a3e5fbcd055596e1496854326ffd17572e3ae42d (diff) | |
| download | gcc-cec97549b781643f55bde34d025c3170309e3646.zip gcc-cec97549b781643f55bde34d025c3170309e3646.tar.gz gcc-cec97549b781643f55bde34d025c3170309e3646.tar.bz2 | |
m68k: don't allow o/o in movdi, movdf, movxf
The movdi, movdf and movxf patterns allow both operands to be offsettable
memory, but output_move_double cannot handle overlapping objects. This is
visible in the failure of gcc.c-torture/execute/pr97073.c when compiled
with LTO (where cprop optimizes out the AND operation; the failure also
occurs without LTO when the AND is removed). Split the constraints so
that the operands cannot both be "o" in the same insn.
* config/m68k/m68k.md (movdi+1, movdf+1, movxf+2): Split
constraints so that the operands cannot both be "o".
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/config/m68k/m68k.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/gcc/config/m68k/m68k.md b/gcc/config/m68k/m68k.md index 1c9a6bf..d732900 100644 --- a/gcc/config/m68k/m68k.md +++ b/gcc/config/m68k/m68k.md @@ -1354,8 +1354,8 @@ }) (define_insn "" - [(set (match_operand:DF 0 "nonimmediate_operand" "=rm,rf,rf,&rof<>") - (match_operand:DF 1 "general_operand" "*rf,m,0,*rofE<>"))] + [(set (match_operand:DF 0 "nonimmediate_operand" "=rm,rf,rf,&rof<>,&rf<>") + (match_operand:DF 1 "general_operand" "*rf,m,0,*rfE<>,*rofE<>"))] ; [(set (match_operand:DF 0 "nonimmediate_operand" "=rm,&rf,&rof<>") ; (match_operand:DF 1 "general_operand" "rf,m,rofF<>"))] "!TARGET_COLDFIRE" @@ -1514,8 +1514,8 @@ [(set_attr "flags_valid" "move")]) (define_insn "" - [(set (match_operand:XF 0 "nonimmediate_operand" "=rm,rf,&rof<>") - (match_operand:XF 1 "nonimmediate_operand" "rf,m,rof<>"))] + [(set (match_operand:XF 0 "nonimmediate_operand" "=rm,rf,&rof<>,&rf<>") + (match_operand:XF 1 "nonimmediate_operand" "rf,m,rf<>,rof<>"))] "! TARGET_68881 && ! TARGET_COLDFIRE" { if (FP_REG_P (operands[0])) @@ -1568,8 +1568,8 @@ ;; movdi can apply to fp regs in some cases (define_insn "" ;; Let's see if it really still needs to handle fp regs, and, if so, why. - [(set (match_operand:DI 0 "nonimmediate_operand" "=rm,r,&ro<>") - (match_operand:DI 1 "general_operand" "rF,m,roi<>F"))] + [(set (match_operand:DI 0 "nonimmediate_operand" "=rm,r,&ro<>,&r<>") + (match_operand:DI 1 "general_operand" "rF,m,ri<>F,roi<>F"))] ; [(set (match_operand:DI 0 "nonimmediate_operand" "=rm,&r,&ro<>,!&rm,!&f") ; (match_operand:DI 1 "general_operand" "r,m,roi<>,fF"))] ; [(set (match_operand:DI 0 "nonimmediate_operand" "=rm,&rf,&ro<>,!&rm,!&f") |