[pypy-dev] Loop invaraints
hakan at debian.org
Sun Aug 29 13:49:23 CEST 2010
On Sun, Aug 29, 2010 at 12:32 PM, Carl Friedrich Bolz <cfbolz at gmx.de> wrote:
> ... but I don't see why this is needed. Wouldn't you rather need the
My thinking was that for the preamble to be removed from the end of a
bridge maintaining the invariant this would be needed? But I might be
> whole trace of the loop including the preamble up to the failing guard?
> This would be bad, because you need to store the full trace then.
OK, so that might be a problem. Maybe it would be possible to extract
what part of the state it would be safe to inherit even if only the
preamble has been processed, i.e. self.pure_operations might be ok?
> P.S.: A bit unrelated, but a comment on the jit-bounds branch: I think
> it would be good if the bounds-related optimizations could move out of
> optimizeopt.py to their own file, because otherwise optimizeopt.py is
> getting really unwieldy. Does that make sense?
Well, class IntBound and the propagate_bounds_ methods could probably
be moved elsewhere, but a lot of the work is done in optimize_...
methods, which I'm not so sure it would make sens to split up.
More information about the Pypy-dev