You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure this is technically a register allocator to-do, but we need a way to scavenge registers during
frame index elimination and spilling for targets that need additional registers for creating large offsets, or
cannot use immediate offsets in addresses during spilling.
Examples of this in the PPC backend include using r0 as a scratch register during frame index elimination
for creating constant offsets larger than 32k, and using r0 as an index register for saving and restoring
vector registers, which can only use reg+reg addressing.
Once this is done, all use of r0 should be removed from the PPC backend.
The text was updated successfully, but these errors were encountered:
Extended Description
I'm not sure this is technically a register allocator to-do, but we need a way to scavenge registers during
frame index elimination and spilling for targets that need additional registers for creating large offsets, or
cannot use immediate offsets in addresses during spilling.
Examples of this in the PPC backend include using r0 as a scratch register during frame index elimination
for creating constant offsets larger than 32k, and using r0 as an index register for saving and restoring
vector registers, which can only use reg+reg addressing.
Once this is done, all use of r0 should be removed from the PPC backend.
The text was updated successfully, but these errors were encountered: