workaround for "error: more than 30 operands in 'asm'"?

[Ian Lance Taylor]

Segher Boessenkool <segher@kernel.crashing.org> writes:

>> I wonder if we could do something more sensible than simply using the
>> constant 30.  Perhaps some function of FIRST_PSEUDO_REGISTER, like
>> FIRST_PSEUDO_REGISTER+20, or FIRST_PSEUDO_REGISTER*2 or even
>> MAX (FIRST_PSEUDO_REGISTER, 29).  This would at least solve the problem
>> here.
>
> Why is there a maximum here at all -- some hugely non-linear
> algorithm or so?

No, just a lot of statically defined arrays.  Having a maximum doesn't
matter much; having a constant matters.

Ian