I have hand-written asm for use in production code, and I would do it again. I also knew exactly what cpu my code would be running on. If I were publishing the code to run on a variety of hardware, I would be very cautious.
Writing your own crypto is very different; the stakes are higher if you get it wrong.
Including the microcode version currently installed into the CPU and gone through the release notes, alongside a profile like V-Tune?
This is definitely not correct. For many SIMDable workloads it's possible to achieve order of magnitude improvements over the compiler.
Re:Optimising Memset and Memcpy
by WalterBright on Sunday November 28, 2021 @01:09PM
(#29371221)
A good heuristic is simply minimize the number of instructions.
I doubt it'd be an issue for memcpy but minimizing the size of a loop body can lead to very counterintuitive speedups now processors have LSDs (loop stream detectors).
I used to do assembly and count cycles, but now I wouldn't dare; it's hardcore compiler and library makers stuff. It's like "don't do your own crypto (optimization)".
Everyone knows why it is so, though - we cannot solve the problem by throwing more Gigahertz at it.