[Python-Dev] Why is Bytecode the way it is? (original) (raw)
Fred L. Drake, Jr. fdrake at acm.org
Fri Jul 9 07:07:19 CEST 2004
- Previous message: [Python-Dev] Why is Bytecode the way it is?
- Next message: [Python-Dev] Why is Bytecode the way it is?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thursday 08 July 2004 09:17 pm, Greg Ewing wrote:
But it would only be worth doing if the cost of these data movements is a substantial fraction of the whole execution time. Does anyone have any timings to suggest that they are?
I'd expect the cost of the data movement to be swamped by overhead of running through the decode/execute. The question is whether increasing the decoding cost a bit is cheaper than the additional trips through the loop.
-Fred
-- Fred L. Drake, Jr.
- Previous message: [Python-Dev] Why is Bytecode the way it is?
- Next message: [Python-Dev] Why is Bytecode the way it is?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]