On 20/09/18 13:46, Richard Sandiford wrote:
Andrew Stubbs writes:
In the case of move_unallocated_pseudos it's because the table
pseudo_replaced_reg only has entries for the new pseudos directly
created by find_moveable_pseudos, not the ones created indirectly.
What I more meant was: where do
Andrew Stubbs writes:
> On 17/09/18 10:22, Richard Sandiford wrote:
>> writes:
>>> The IRA pass makes an assumption that any pseudos created after the
>>> pass begins
>>> were created explicitly by the pass itself and therefore will have
>>> corresponding entries in its other tables.
>>>
>>> The
On 17/09/18 10:22, Richard Sandiford wrote:
writes:
The IRA pass makes an assumption that any pseudos created after the pass begins
were created explicitly by the pass itself and therefore will have
corresponding entries in its other tables.
The GCN back-end, however, often creates additional
writes:
> The IRA pass makes an assumption that any pseudos created after the pass
> begins
> were created explicitly by the pass itself and therefore will have
> corresponding entries in its other tables.
>
> The GCN back-end, however, often creates additional pseudos, in expand
> patterns, to r
The IRA pass makes an assumption that any pseudos created after the pass begins
were created explicitly by the pass itself and therefore will have
corresponding entries in its other tables.
The GCN back-end, however, often creates additional pseudos, in expand
patterns, to represent the necessary
