From: Uros Bizjak Date: Mon, 9 Sep 2024 20:33:52 +0000 (+0200) Subject: i386: Use offsetable address constraint for double-word memory operands X-Git-Tag: basepoints/gcc-16~6001 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1da79de5275de82bc810d2f8d70fbc98dbce3da5;p=thirdparty%2Fgcc.git i386: Use offsetable address constraint for double-word memory operands 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 (*insvdi_lowpart_1): Use "o" constraint instead of "m" for double-word mode memory operands. (*add3_doubleword_zext): Ditto. (*addv4_doubleword_1): Use "jO" constraint instead of "jM" for double-word mode memory operands. --- diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md index 0fae3c1eb87..8d269feee83 100644 --- a/gcc/config/i386/i386.md +++ b/gcc/config/i386/i386.md @@ -3707,7 +3707,7 @@ [(set (match_operand:DI 0 "nonimmediate_operand" "=ro,r,r,&r") (any_or_plus:DI (and:DI - (match_operand:DI 1 "nonimmediate_operand" "r,m,r,m") + (match_operand:DI 1 "nonimmediate_operand" "r,o,r,o") (match_operand:DI 3 "const_int_operand" "n,n,n,n")) (zero_extend:DI (match_operand:SI 2 "nonimmediate_operand" "r,r,m,m"))))] @@ -6461,7 +6461,7 @@ (plus: (zero_extend: (match_operand:DWIH 2 "nonimmediate_operand" "rm,r,rm,r")) - (match_operand: 1 "nonimmediate_operand" "0,0,r,m"))) + (match_operand: 1 "nonimmediate_operand" "0,0,r,o"))) (clobber (reg:CC FLAGS_REG))] "ix86_binary_operator_ok (UNKNOWN, mode, operands, TARGET_APX_NDD)" "#" @@ -7703,7 +7703,7 @@ (eq:CCO (plus: (sign_extend: - (match_operand: 1 "nonimmediate_operand" "%0,rjM")) + (match_operand: 1 "nonimmediate_operand" "%0,rjO")) (match_operand: 3 "const_scalar_int_operand" "n,n")) (sign_extend: (plus: