Changes by A.M. Kuchling li...@amk.ca:
--
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
versions: +Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
___
___
Changes by Chris Leary christopher.le...@cornell.edu:
--
nosy: +cdleary
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
___
___
A.M. Kuchling li...@amk.ca added the comment:
I finally got around to benchmarking this change, and unfortunately the results
are not good.
I used the regex tests in the Unladen Swallow test suite, regex_effbot and
regex_v8. The tests are written for Python 2.x, but the fixes for 3.x are
A.M. Kuchling li...@amk.ca added the comment:
Actually, I really want someone to verify that measurement. As a control, I
tried running the call_method benchmark (after a few more xrange fixes). The
Python 3.x trunk version with my patch is measured as 1.0227x slower, even
though the patch
Antoine Pitrou pit...@free.fr added the comment:
You should disassemble the output (or produce assembler from gcc) and check
that the various indirect jumps at the end of each case block don't get merged
into a single shared indirect jump.
Or perhaps it's simply that regular expression
Georg Brandl ge...@python.org added the comment:
_sre is listed in Modules/Setup, so it will be a built-in module by default.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
Changes by Georg Brandl ge...@python.org:
--
title: Computed-goto patch - Computed-goto patch for RE engine
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
___
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7593
___
___
Python-bugs-list mailing
Antoine Pitrou pit...@free.fr added the comment:
On the principle nothing looks wrong. There are some tabs-vs-spaces
issues in _sre.c. Can some out-of-bounds crash be triggered if an opcode
is greater than 33?
It needs some benchmarks to know whether it's efficient. Also, I think
it would be
10 matches
Mail list logo