Hello, > I have been doing some performance experiments with memcmp, and I was > surprised that memcmp wasn't faster than it was in Python. I did a whole, > long analysis and came up with some very simple results. > > Before I put in a tracker bug report, I wanted to present my findings > and make sure they were repeatable to others (isn't that the nature > of science? ;) as well as offer discussion. Thanks for the analysis. Non-bugfix work now happens on Python 3, where the str type is Python 2's unicode type. Your recommendations would have to be revisited under that light. Have you reported gcc's "outdated optimization" issue to them? Or is it already solved in newer gcc versions? Under glibc-based systems, it seems we can't go wrong with the system memcpy function. If gcc doesn't get in the way, that is. Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4