Hi Tim,
On 29 April 2014 13:22, Tim Felgentreff wrote:
> Maybe it's useful to add that even without any changes to the SPy VM,
> frame objects in loops are nicely virtualized in the tests (where they
> are executing at a stack depth of 1), but already if we execute the
> loop at a stack depth of
Hi Armin,
We might again talk past each other. What I believe I understand
> behind what you're saying: you're looking at the outermost frame (the
> one in which the looping occurs). This frame is not a virtualizable
> (because you don't have any), and is also not a virtual (because it
> already
On Wed, Apr 30, 2014 at 1:11 PM, Anton Gulenko <
[email protected]> wrote:
> I'll try to make the example that Tim mentioned more clear.
> Building up the deep stack was done INSIDE the loop. It was also the only
> thing that happened inside the loop.
> That's why we expecte
Hi Anton,
On 30 April 2014 13:11, Anton Gulenko
wrote:
> Ok, so virtuals and virtualizables are two unrelated mechanisms?
> How does the optimizer decide which writes to virtualizable fields it is
> able to eliminate?
It's not decided by the optimizer. A virtualizable structure has got
a static
