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 vstinner
Recipients Neil.Hodgson, ethan.furman, ezio.melotti, georg.brandl, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2013-04-09.21:57:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365544629.84.0.46547354358.issue17615@psf.upfronthosting.co.za>
In-reply-to
Content
"Including the wmemcmp patch did not improve the times on MSC v.1600 32 bit - if anything, the performance was a little slower for the test I used:"

I tested my patch on Windows before the commit and I saw similar performances with and without wmemcmp().

I checked again and you are true: performances are *a little bit* worse using wmemcmp().

"Looking at the assembler, there is a real call to wmemcmp which adds some time and wmemcmp does not seem to be optimized compared to a simple loop."

You should be true. I reverted the patch for 16-bit wchar_t to use a dummy loop instead. 16-bit wchar_t can only be found on Windows, isn't it?
History
Date User Action Args
2013-04-09 21:57:09vstinnersetrecipients: + vstinner, georg.brandl, pitrou, ezio.melotti, ethan.furman, python-dev, serhiy.storchaka, Neil.Hodgson
2013-04-09 21:57:09vstinnersetmessageid: <1365544629.84.0.46547354358.issue17615@psf.upfronthosting.co.za>
2013-04-09 21:57:09vstinnerlinkissue17615 messages
2013-04-09 21:57:09vstinnercreate