Displaying 2 results from an estimated 2 matches for "vgpr39".
Did you mean:
vgpr3
2020 May 29
2
Dynamically determine the CostPerUse value in the register allocator.
...he initial reserved 32 argument registers, all VGPRs are callee-saved registers (VGPR32 - VGPR255).
With the new ABI:
We made VGPR32 - VGPR255 into equal number of callee-saved and caller-saved registers.
For the same occupancy reason, these two sets are interleaved at a split boundary of 8.
VGPR32-VGPR39 (Caller-saved)
VGPR40-VGPR47 (Callee-saved)
VGPR48-VGPR55 (Caller-saved)
-
-
VGPR248-VGPR255 (Callee-saved)
With the new ABI, the allocator's preference for callee-saved vs caller-saved depends on the input program.
RA may end up allocating more caller-saved registe...
2020 May 30
2
Dynamically determine the CostPerUse value in the register allocator.
...e
> callee-saved registers (VGPR32 - VGPR255).
>
> With the new ABI:
>
> We made VGPR32 - VGPR255 into equal number of callee-saved and
> caller-saved registers.
>
> For the same occupancy reason, these two sets are interleaved at a split
> boundary of 8.
>
> VGPR32-VGPR39 (Caller-saved)
>
> VGPR40-VGPR47 (Callee-saved)
>
> VGPR48-VGPR55 (Caller-saved)
>
> -
>
> -
>
> VGPR248-VGPR255 (Callee-saved)
>
>
>
> With the new ABI, the allocator’s preference for callee-saved vs
> caller-saved depends on...