A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-February/032857.html below:

native code compiler? (or, OCaml vs. Python)

[Python-Dev] Re: native code compiler? (or, OCaml vs. Python) [Python-Dev] Re: native code compiler? (or, OCaml vs. Python)Skip Montanaro skip@pobox.com
Mon, 3 Feb 2003 14:54:56 -0600
    Neal> Right now JUMP_IF_(TRUE, FALSE) keep their computed value on the
    Neal> stack.  They are always followed by POP_TOP.  If the JUMP_IF_*
    Neal> removed the value, it would be one less trip through eval_frame
    Neal> loop (no POP_TOP).  I've got a patch for this which fixes 5 of the
    Neal> 8 cases where JUMP_IF_* are generated.  The problem with the
    Neal> remaining 3 cases is that a jump to a jump occurs.  By removing
    Neal> the jump to a jump, that should also help performance.

See my peephole optimizer reference in an earlier note which (used to)
handle such stuff.  Perhaps it should be dusted off.

Skip



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4