Message82737
Jeffrey: updated the patch to address your concerns.
Martin: I'm not sure I completely understand it either, though it seems
similar to issue4477. In the course of developing this patch, I tried
also #ifdef'ing out all usages of the Py_Py3kWarningFlag global. This
actually made things slower by around 5% across all the benchmarks I
tested. Could be pipeline stalls or a code size issue, I really don't know.
I'm not 100% convinced that something like this should go into CPython,
as a different compiler/hardware combination could well render it moot.
I mostly wanted a record of it, in case those few Python deployments
with homogeneous compilers/hardware across their machines that might
care about 1% better performance are interested. |
|
Date |
User |
Action |
Args |
2009-02-26 01:16:54 | collinwinter | set | recipients:
+ collinwinter, loewis, brett.cannon, pitrou, jyasskin |
2009-02-26 01:16:54 | collinwinter | set | messageid: <1235611014.4.0.735009432249.issue5362@psf.upfronthosting.co.za> |
2009-02-26 01:16:52 | collinwinter | link | issue5362 messages |
2009-02-26 01:16:51 | collinwinter | create | |
|