"Paulo J. Matos" writes:
> On 26/09/11 17:23, Ian Lance Taylor wrote:
>>
>> The function added_clobbers_hard_reg_p is a generated function. So
>> another approach would be some sort of attribute which directs the
>> generator (genemit) to ignore certain hard registers.
>>
>
> This definitely soun
On 26/09/11 17:23, Ian Lance Taylor wrote:
The function added_clobbers_hard_reg_p is a generated function. So
another approach would be some sort of attribute which directs the
generator (genemit) to ignore certain hard registers.
This definitely sounds like the best approach for my specific
"Paulo J. Matos" writes:
> My question is, should added_clobbers_hard_reg_p take FLAGS_REGNUM
> into consideration and allow it in a clobber, just as it allows a
> scratch?
There is no middle-end concept of FLAGS_REGNUM (barring reg-stack.c
which is really a target-specific pass). Some targets
Hi,
I was tracking down an assertion failure in GCC which occured while I
was trying to bend some GCC constraints.
I came accross this function `insn_invalid_p', which calls
`added_clobbers_hard_reg_p' and before calling it, has the comment:
/* If we have to add CLOBBERs, fail if we have to
