[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-03 Thread Stefan Krah
Stefan Krah added the comment: I'm surprised, too, but after a couple of retries the results stay the same. On an i7 there's also a difference, but not quite as large. I'm using b16527f84774.diff, which applies cleanly apart from importlib.h (which I just regenerated). With an increased loop

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-03 Thread Stefan Krah
Stefan Krah added the comment: BTW, there's no general slowdown on the Core2 Duo: In the patched version, the telco benchmark is consistently 4% faster. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17611

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-03 Thread Antoine Pitrou
Antoine Pitrou added the comment: BTW, there's no general slowdown on the Core2 Duo: In the patched version, the telco benchmark is consistently 4% faster. It's customary for even innocent changes in ceval to produce small changes in some benchmarks. It's only really important to consider the

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-03 Thread Mark Dickinson
Changes by Mark Dickinson dicki...@gmail.com: -- nosy: +mark.dickinson ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17611 ___ ___

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-03 Thread Stefan Krah
Stefan Krah added the comment: Antoine Pitrou rep...@bugs.python.org wrote: It's customary for even innocent changes in ceval to produce small changes in some benchmarks. It's only really important to consider the global average. Yes, the float benchmark appears to be particularly sensitive.

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-03 Thread Trent Nelson
Changes by Trent Nelson tr...@snakebite.org: -- nosy: +trent ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17611 ___ ___ Python-bugs-list mailing

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-01 Thread Mark Shannon
New submission from Mark Shannon: The handling of pseudo exceptions (return, break and continue) are currently handled in the interpreter. This make the interpreter loop more complex and slower than it needs to be. This change moves the handling of pseudo exceptions into the compiler. The

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-01 Thread Mark Shannon
Changes by Mark Shannon m...@hotpy.org: -- keywords: +patch Added file: http://bugs.python.org/file29646/b16527f84774.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17611 ___

[issue17611] Move unwinding of stack for pseudo exceptions from interpreter to compiler.

2013-04-01 Thread Raymond Hettinger
Raymond Hettinger added the comment: Additional effect: Destabilizes lots of code that has had a decade to mature. It messes with the compiler, the eval loop, the peephole optimizer, the disassembler, every third-party tool that examines or alters byte codes, any tool or VM that implements

<    1   2