[RFC] avoiding too narrow register classes in reload

[Bernd Schmidt]

> This is what causes the problem I'm running into: if this alternative
> is selected (and it will often be), we end up forced to use one of the
> first two argument registers for the reload, and this will fail if the
> reload is needed in the middle of a function call sequence.

What does the insn that it's trying to reload look like?


Bernd