i386: Use offsetable address constraint for double-word memory operands, part 2

Double-word memory operands are accessed as their high and low part, so the
memory location has to be offsettable.  Use "o" constraint instead of "m"
for double-word memory operands.

gcc/ChangeLog:

	* config/i386/i386.md (*insvti_lowpart_1): Use "o" constraint
	instead of "m" for double-word mode memory operands.
This commit is contained in:
Uros Bizjak 2024-09-12 16:28:10 +02:00
parent 25ac2bb57a
commit 8c01976b8e

View File

@ -3685,7 +3685,7 @@
[(set (match_operand:TI 0 "nonimmediate_operand" "=ro,r,r,&r")
(any_or_plus:TI
(and:TI
(match_operand:TI 1 "nonimmediate_operand" "r,m,r,m")
(match_operand:TI 1 "nonimmediate_operand" "r,o,r,o")
(match_operand:TI 3 "const_scalar_int_operand" "n,n,n,n"))
(zero_extend:TI
(match_operand:DI 2 "nonimmediate_operand" "r,r,m,m"))))]