[issue9866] Inconsistencies in tracing list comprehensions
report at bugs.python.org
Tue Sep 21 17:27:58 CEST 2010
Alexander Belopolsky <belopolsky at users.sourceforge.net> added the comment:
I have found the root cause of these differences. The trace function is not called when the opcode is successfully predicted. When computed gotos are enabled, opcode prediction is disabled as explained in the following comment in ceval.c:
Opcode prediction is disabled with threaded code, since the latter allows
the CPU to record separate branch prediction information for each
Note that this issue is similar to #884022 which was resolved by disabling opcode prediction in dynamic profile builds.
Given that opcode prediction if off by default, I don't see much of the reason to try to improve tracing of predicted opcodes.
assignee: -> belopolsky
resolution: -> out of date
status: open -> pending
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list