This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Aahz, aahz, mark.dickinson, pitrou, rhettinger, stutzbach
Date 2010-10-05.15:03:09
SpamBayes Score 6.880817e-05
Marked as misclassified No
Message-id <1286290985.3399.2.camel@localhost.localdomain>
In-reply-to <1286290269.83.0.245940939312.issue9800@psf.upfronthosting.co.za>
Content
> I did some spelunking.  Guido committed the similar optimization in r8306.    The diff is at:
> http://svn.python.org/view/python/trunk/Python/ceval.c?r1=8087&r2=8306
> 
> His commit message was:
> 
>     Huge speedup by inlining some common integer operations:
>     int+int, int-int, int <compareop> int, and list[int].
>     (Unfortunately, int*int is way too much code to inline.)
> 
>     Also corrected a NULL that should have been a zero.
> 
> It's possible that these kinds of optimizations were worthwhile with
> PyInt but aren't worthwhile with PyLong.

It also doesn't say the individual contribution of each optimization,
and it also doesn't say on which kind of workloads the "huge speedup"
was witnessed (I would say that pystone is a possibility, or perhaps
even some timeit micro-benchmark).
History
Date User Action Args
2010-10-05 15:03:11pitrousetrecipients: + pitrou, rhettinger, aahz, mark.dickinson, stutzbach, Aahz
2010-10-05 15:03:09pitroulinkissue9800 messages
2010-10-05 15:03:09pitroucreate