[Vm-dev] Eliot's BlockClosure model questions

Clément Bera bera.clement at gmail.com
Mon Jul 29 20:28:37 UTC 2013


2013/7/29 tim Rowledge <tim at rowledge.org>

>
>
> On 29-07-2013, at 1:54 AM, Clément Bera <bera.clement at gmail.com> wrote:
> > - Lastly, does VW have the tempVector optimization for escaping write
> temporaries in their blockClosure ? It seems they have not (I don't see any
> reference to it in VW 7). Did Pharo/Squeak blocks earns a lot of speed or
> memory with this optimization ?
>
> Assuming you're talking about what I think you are talking about, VW had
> it around 12years ago; I remember Eliot explaining it to me at least three
> times before I quite got it. I happened to be visiting with him for lunch
> on the day when it first worked well, IIRC.
>

Thanks for your answer. So they have it. Actually on second thoughts it may
be that blocks need the temp vector to work with the stack mapping: if a
block outlive its homeContext, the homeContext variables may be overridden
in the stack.

It is just that I see no reference to it in VW class comments. Perhaps it
is only VM details hidden from the user.

>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Useful Latin Phrases:- Re vera, potas bene = Say, you sure are drinking a
> lot.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20130729/e6a1abdd/attachment.htm


More information about the Vm-dev mailing list