Jeff Law writes:
> Finding a way to drop the naked clobbers/uses would be a better way
> forward. I'm a bit surprised we need them as much as we apparently do.
> We're conflating issues a bit here though.
FWIW, I think they're a really useful feature. E.g. they help when
modelling the lifetimes
On Thu, 2020-01-23 at 11:43 +, Richard Sandiford wrote:
> Jeff Law writes:
> > On Wed, 2020-01-22 at 12:02 +, Richard Sandiford wrote:
> > > One consequence of r276318 was that cselib now preserves sp-based
> > > values across function calls. This in turn convinced cprop to
> > > replace
Jeff Law writes:
> On Wed, 2020-01-22 at 12:02 +, Richard Sandiford wrote:
>> One consequence of r276318 was that cselib now preserves sp-based
>> values across function calls. This in turn convinced cprop to
>> replace the clobber in:
>>
>>(set (reg PSUEDO) (reg sp))
>>...
>>(ca
On Wed, 2020-01-22 at 12:02 +, Richard Sandiford wrote:
> One consequence of r276318 was that cselib now preserves sp-based
> values across function calls. This in turn convinced cprop to
> replace the clobber in:
>
>(set (reg PSUEDO) (reg sp))
>...
>(call ...)
>...
>(clob
One consequence of r276318 was that cselib now preserves sp-based
values across function calls. This in turn convinced cprop to
replace the clobber in:
(set (reg PSUEDO) (reg sp))
...
(call ...)
...
(clobber (mem:BLK (reg sp)))
with:
(clobber (mem:BLK (reg PSEUDO)))
But I dou
