Rakudo *Needs* Register Allocation

Vasily Chekalkin bacek at bacek.com
Mon Jun 28 21:35:53 UTC 2010

On Mon, Jun 28, 2010 at 10:26 AM, chromatic <chromatic at wgz.org> wrote:
> On Sunday 27 June 2010 at 16:33, Andrew Whitworth wrote:
>> Do you think it should be
>> part of normal POST operation, or added as an optional optimization
>> step? I ask because we might want multiple pluggable/selectable
>> allocators, and we may want to turn off the fancier ones entirelywhere
>> speed is an issue.
> I believe that POST already has some idea of the lifespan of registers (as it
> has to track their names), but I'm pretty sure it does no basic block tracing.
> It'd be nice to take advantage of the lifespan information where it's
> available.

POST from parrot trunk doesn't have it. It's way too stringish. POST
from PIRATE has.


More information about the parrot-dev mailing list