News for hackers. Stuff that matters.
Re:Optimising Memset and Memcpy by astrobe_ on Sunday November 28, 2021 @08:11AM (#29368638)
CPU makers add so many complicated features to let users optimize their programs that it takes too much knowledge for mere mortals to optimize their programs - That you have to rely on heuristics and measures, as it is usually and wisely advised, is a bit unsatisfying. That's sort of ironic, in a way.

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.

Re:Optimising Memset and Memcpy by cout on Sunday November 28, 2021 @08:40AM (#29368814)
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.

Re:Optimising Memset and Memcpy by pjmlp on Monday November 29, 2021 @10:12AM (#29380743)
Including the microcode version currently installed into the CPU and gone through the release notes, alongside a profile like V-Tune?
Re:Optimising Memset and Memcpy by kierank on Sunday November 28, 2021 @04:57PM (#29373452)
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.
Re:Optimising Memset and Memcpy by mhh__ on Sunday November 28, 2021 @01:30PM (#29371453)
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).
Re:Optimising Memset and Memcpy by jeffbee on Sunday November 28, 2021 @04:20PM (#29373157)
If you make them too small it can lead to counterintuitive slowdowns.