[pypy-dev] [pypy-commit] pypy default: investigate mark_opaque_ptr

[Hakan Ardo]

On Tue, Oct 14, 2014 at 9:26 AM, Armin Rigo <arigo at tunes.org> wrote:
>
> I'm not sure: the logic in optimizeopt/heap.py seems to be "if it's an
> opaque pointer, and if we don't know its class, then don't move it".
> According to this logic, operations on RPython instances (like
> GUARD_CLASS) can still be moved to the short preamble.  Maybe I'm
> missing something else?

I see. Yes, there is the logic of ShortBoxes.assumed_classes which is
supposed to make sure never to inline a short_preamble in cases where
the class of the opaque pointer is not already known. This logic could
probably be killed with your solution.

-- 
Håkan Ardö