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/2011-August/113367.html below:

[Python-Dev] Python 3 optimizations continued...

[Python-Dev] Python 3 optimizations continued... [Python-Dev] Python 3 optimizations continued...Antoine Pitrou solipsis at pitrou.net
Tue Aug 30 19:38:06 CEST 2011
On Tue, 30 Aug 2011 08:27:13 -0700
stefan brunthaler <stefan at brunthaler.net> wrote:
> >> Changing the bytecode width wouldn't make the interpreter more complex.
> >
> > No, but I think Stefan is proposing to add a *second* byte code format,
> > in addition to the one that remains there. That would certainly be an
> > increase in complexity.
> >
> Yes, indeed I have a more straightforward instruction format to allow
> for more efficient decoding. Just going from bytecode size to
> word-code size without changing the instruction format is going to
> require 8 (or word-size) times more memory on a 64bit system.

Do you really need it to match a machine word? Or is, say, a 16-bit
format sufficient.

Regards

Antoine.
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