https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114591
--- Comment #7 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Hongtao Liu from comment #5) > > My experience is memory cost for the operand with rm or separate r, m is > > different which impacts RA decision. > > > > https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595573.html > > Change operands[1] alternative 2 from m -> rm, then RA makes perfect > decision. Oh, you are also the author of the above patch ;) Can you please take the issue from here and perhaps review other x86 patterns for unoptimal constraints? I was always under impression that rm and separate "r,m" are treated in the same way...
