[issue11087] Speeding up the interpreter with a few lines of code

Antoine Pitrou added the comment: > Not at the expense of introducing undefined behaviour. I suggest > closing this. ok, let's do it. -- resolution: -> rejected stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue11087] Speeding up the interpreter with a few lines of code

Mark Dickinson added the comment: > ... is this worth pursuing? Not at the expense of introducing undefined behaviour. I suggest closing this. -- nosy: +mark.dickinson ___ Python tracker _

[issue11087] Speeding up the interpreter with a few lines of code

Mark Lawrence added the comment: 3-4% faster in some cases is better than a kick in the head but is this worth pursuing? -- nosy: +BreamoreBoy ___ Python tracker ___ ___

[issue11087] Speeding up the interpreter with a few lines of code

Antoine Pitrou added the comment: Ok, things are at best 3-4% faster here (often unchanged). -- versions: -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___

[issue11087] Speeding up the interpreter with a few lines of code

Changes by Georg Brandl : -- assignee: -> pitrou nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11087] Speeding up the interpreter with a few lines of code

New submission from Jurjen N.E. Bos : I found a very simple way to improve the speed of CPython a few percent on the most common platforms (i.e. x86), at the cost of only a few lines of code in ceval.c The only problem is that I don't have any experience in patch submission. Here are the sugge