Richard Sandiford writes:
> Richard Sandiford writes:
>> Bernd Schmidt writes:
>>> On 09/25/11 19:16, Richard Sandiford wrote:
The last bit is indirect, via a new HARD_REG_SET called operand_reg_set.
And this set is the reason why I'm sending the patch now. The MIPS16 port
has al
Richard Sandiford writes:
> Bernd Schmidt writes:
>> On 09/25/11 19:16, Richard Sandiford wrote:
>>> The last bit is indirect, via a new HARD_REG_SET called operand_reg_set.
>>> And this set is the reason why I'm sending the patch now. The MIPS16 port
>>> has always had a problem with the HI and
Bernd Schmidt writes:
> On 09/25/11 19:16, Richard Sandiford wrote:
>> The last bit is indirect, via a new HARD_REG_SET called operand_reg_set.
>> And this set is the reason why I'm sending the patch now. The MIPS16 port
>> has always had a problem with the HI and LO registers: they can only be
>
On 09/25/11 19:16, Richard Sandiford wrote:
> The last bit is indirect, via a new HARD_REG_SET called operand_reg_set.
> And this set is the reason why I'm sending the patch now. The MIPS16 port
> has always had a problem with the HI and LO registers: they can only be
> set by multiplication and d
This patch tries to fix one thing that has bugged me for a while:
there's no way of explicitly saying that some hard registers are
only available with certain target options. The usual approach is
to make TARGET_CONDITIONAL_REGISTER_USAGE fix any registers that
don't exist, but this doesn't in its
