4 ms·
From my understanding, looping avx512 or avx2 mov might be faster than rep stos in many cases.
by dragontamer 6y ago
From my understanding, looping avx512 or avx2 mov might be faster than rep stos in many cases.
- jeffbee 6y agoThe number of such cases is decreasing, though. Recent (ICL and "later" whatever that means) Intel cores have fast-short-rep-movsb which reduces the startup time of the REP. Considering the icache pressure of a hyperoptimized memcpy, it is probably the right way to go for new code. If you're interested see Google's paper, AsmDB: Understanding and Mitigating Front-End Stalls, section 4.4 Memcmp and the perils of micro-optimization, in which they say that REP CMPS beats glibc memcmp in full-scale benchmarks. "On large-footprint workloads like websearch, it reduced cycles in memcmp more than twofold and showed an overall 0.5%-1% end-toend performance improvement." And that was on Haswell, before people started selling parts with "fast short cmpsb"
- deleted 6y ago[deleted]
- dragontamer 6y agoGood to hear. Rep movs is the obvious way to represent memmove and memcpy. Avx moves should have never been faster than that sequence.