I'm less of an expert than either of you, but still have a piece of
advice:
If you use CPU specific code, I'd suggest all of the CPU specific code
be encapsulated within one or a very few objects, modules or data
structures with associated functions, so that if the unexpected happens
and you switc
I'm not much of an expert, but the first thing that comes to mind is the
binary size and speed.
If you only need to implement the code once, and have a single optimized
version, the output will be smaller, and probably a bit faster.
--
Rabin
On Fri, 20 Aug 2021 at 11:54, Lev Olshvang wrote:
Morning people of the Linux ! Recently I came to a question I do not know the answer to although I am with Linux for >20 years, I am talking about the CPU architecture features likes SIMD, SSE, AES, ... and related gcc CPU architecture switches-maes, -msse3, -msse4 -mrdrand are examples of such gc
