A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-July/046012.html below:

[Python-Dev] Why is Bytecode the way it is?

[Python-Dev] Why is Bytecode the way it is? [Python-Dev] Why is Bytecode the way it is?Fred L. Drake, Jr. fdrake at acm.org
Fri Jul 9 07:07:19 CEST 2004
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.  <fdrake at acm.org>

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4