> It did match the first alternative (alternative 0), but it matched the > constraints Y/Y/m.
It shouldn't match Y as those are for near addresses (unless it's only matching MEM==MEM), and the ones in the insn are far, but ... > Reload doesn't have any concept of two different kinds of memory > operands which can't be converted via reloads. If the constraint > accepts mem, and we have a mem operand, then it will always assume > that the problem is with the address and reload it. ... this sounds like it could be a problem for me :-P
