From: Uros Bizjak Date: Thu, 12 Sep 2024 14:28:10 +0000 (+0200) Subject: i386: Use offsetable address constraint for double-word memory operands, part 2 X-Git-Tag: basepoints/gcc-16~5949 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8c01976b8e34eaa2483ab37d1bd18ebc5c8ada95;p=thirdparty%2Fgcc.git 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. --- diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md index 8d269feee83..c0441514949 100644 --- a/gcc/config/i386/i386.md +++ b/gcc/config/i386/i386.md @@ -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"))))]