This across the board speedup of the python byte code looks promising! I'm
not familiar enough with that part of the code to review it but here's a big
+1
to make sure someone else takes a look.
On Sat, Mar 22, 2008 at 4:07 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
> Wow, thanks to both
Wow, thanks to both of you (Phillip & Skip) for the fast answers.
Just in case anyone has time to spare, I have more pesky questions (and a
working patch :-)) in the aforementioned bug entry
(http://bugs.python.org/issue2459).
Regards
Antoine.
___
Py
At 10:43 PM 3/22/2008 +, Antoine Pitrou wrote:
>- Why are there both relative and absolute jump instructions? The traditional
>rationale for relative jumps (apart from position-independent code)
>is to allow
>for shorter operand sizes; but Python opcodes all have the same operand size
Actuall
Antoine> - Why are there both relative and absolute jump instructions?
The best place to search for the reasons behind this is Python/compile.c.
(JUMP_ABSOLUTE can jump backwards.) There have been lots and lots of
changes to the Python virtual machine the past few years. When trying to
under
Hi,
I'm attempting some bytecode tweaks (see http://bugs.python.org/issue2459) and
I've got two questions about jump instructions:
- Why are there both relative and absolute jump instructions? The traditional
rationale for relative jumps (apart from position-independent code) is to allow
for shor
