[gcc r13-853] x86: correct bmi2_umul<mode><dwi>3_1's MEM_P() uses

[gcc r13-853] x86: correct bmi2_umul<mode><dwi>3_1's MEM_P() uses

[Jan Beulich]

https://gcc.gnu.org/g:c89298404071e3b42eb7e2bfbdbaa45573538b53

commit r13-853-gc89298404071e3b42eb7e2bfbdbaa45573538b53
Author: Jan Beulich <jbeulich@suse.com>
Date:   Mon May 30 11:29:59 2022 +0200

    x86: correct bmi2_umul<mode><dwi>3_1's MEM_P() uses
    
    It's pretty clear that the operand numbers in the MEM_P() checks are
    off by one, perhaps due to a copy-and-paste oversight (unlike in most
    other places here we're dealing with two outputs).
    
    gcc/
    
            * config/i386/i386.md (bmi2_umul<mode><dwi>3_1): Correct MEM_P()
            arguments.

Diff:
---
 gcc/config/i386/i386.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/i386/i386.md b/gcc/config/i386/i386.md
index 602dfa799bf..17bdbd93c4b 100644
--- a/gcc/config/i386/i386.md
+++ b/gcc/config/i386/i386.md
@@ -8465,7 +8465,7 @@
 			(zero_extend:<DWI> (match_dup 3)))
 	    (match_operand:QI 4 "const_int_operand" "n"))))]
   "TARGET_BMI2 && INTVAL (operands[4]) == <MODE_SIZE> * BITS_PER_UNIT
-   && !(MEM_P (operands[1]) && MEM_P (operands[2]))"
+   && !(MEM_P (operands[2]) && MEM_P (operands[3]))"
   "mulx\t{%3, %0, %1|%1, %0, %3}"
   [(set_attr "type" "imulx")
    (set_attr "prefix" "vex")