2 ms·
> the question is: how should we write code today? The only thing that matters today is how fast the code works on today’s hardware. To illustrate, see how I h
by Const-me 6y ago
> the question is: how should we write code today?
The only thing that matters today is how fast the code works on today’s hardware. To illustrate, see how I have emulated neon’s vst3q_s16 with SSE: https://github.com/Const-me/DtsDecoder/blob/master/Utils/store3-sse.hpp https://github.com/Const-me/DtsDecoder/blob/master/Utils/sto... However, not all of them can be emulated in a fast enough manner.
> specifying the memory-moves explicitly, and then working on a "pshufb compiler/optimizer" of sorts is what we need.
I’ll consider that approach when I’ll see that compiler/optimizer working, and producing output comparable to manually-written code. Until then I think that’s a “sufficiently smart compiler” class of problems. These are rarely ever solved, IMO. For example, we don’t have generally useful auto-vectorizers in C compilers despite two decades of R&D, even the best of them (clang, intel) are still very limited.