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 pitrou, serhiy.storchaka, vstinner
Date 2012-03-27.13:57:50
SpamBayes Score 0.0010189968
Marked as misclassified No
Message-id <1332856670.84.0.0638698424463.issue14419@psf.upfronthosting.co.za>
In-reply-to
Content
> This may also depend on the processor and compiler. I have AMD Athlon
> 64 X2 4600+ (2-core, 2.4GHz, 512 KB cache) and use gcc 4.4.3 on 32-bit 
> Linux.

Then by choosing a string length that exceeds the L2 cache size, you may have found an ideal case for your optimization. Basically you're doing the error checking and the memcpy in one single pass.

Honestly I'm not sure that's worth the hassle. ASCII-decoding is already very fast for shorter strings.

(no need to pass "-n" or "-r" to timeit, it will figure out adequate numbers by itself)
History
Date User Action Args
2012-03-27 13:57:50pitrousetrecipients: + pitrou, vstinner, serhiy.storchaka
2012-03-27 13:57:50pitrousetmessageid: <1332856670.84.0.0638698424463.issue14419@psf.upfronthosting.co.za>
2012-03-27 13:57:50pitroulinkissue14419 messages
2012-03-27 13:57:50pitroucreate