Re: [Python-Dev] Improving the bytecode

On 05.06.16 21:24, Raymond Hettinger wrote: On Jun 4, 2016, at 1:08 AM, Serhiy Storchaka wrote: 1. http://bugs.python.org/issue27129 Make the bytecode more 16-bit oriented. I don' think this should be done. Adding the /2 and *2 just complicates the code and messes with

Re: [Python-Dev] Improving the bytecode

> On Jun 4, 2016, at 1:08 AM, Serhiy Storchaka wrote: > > Following the converting 8-bit bytecode to 16-bit bytecode (wordcode), there > are other issues for improving the bytecode. > > 1. http://bugs.python.org/issue27129 > Make the bytecode more 16-bit oriented. I don'

Re: [Python-Dev] Improving the bytecode

On 04/06/16 10:02, Eric Snow wrote: You should get in touch with Mark Shannon, while you're working on ceval. He has some definite improvements that can be made to the eval loop. See http://bugs.python.org/issue17611 for my suggested improvements. I've made a new comment there. Cheers, Mark.

Re: [Python-Dev] Improving the bytecode

You should get in touch with Mark Shannon, while you're working on ceval. He has some definite improvements that can be made to the eval loop. -eric On Sat, Jun 4, 2016 at 2:08 AM, Serhiy Storchaka wrote: > Following the converting 8-bit bytecode to 16-bit bytecode

Re: [Python-Dev] Improving the bytecode

It's not on the list but I'm hoping to convince Dino to work on END_FINALLY to be a bit more sane. On Sat, Jun 4, 2016, 01:17 Serhiy Storchaka wrote: > Following the converting 8-bit bytecode to 16-bit bytecode (wordcode), > there are other issues for improving the

[Python-Dev] Improving the bytecode

Following the converting 8-bit bytecode to 16-bit bytecode (wordcode), there are other issues for improving the bytecode. 1. http://bugs.python.org/issue27129 Make the bytecode more 16-bit oriented. 2. http://bugs.python.org/issue27140 Add new opcode BUILD_CONST_KEY_MAP for building a dict