nemequ1729

8 ms·

1.
by nemequ1729 6y ago
> Not sure where you got that from... xsimd will detect your instruction set automatically. Do you mean that if you're distributing a single binary then you'll need to compile for the lowest common denominator? No, what I mean
2.
by nemequ1729 6y ago
> I'd like to commend the authors for embarking on this. As the crazy bastard who started SIMDe, thanks! I'm very concerned about portability, so unfortunately just using clang isn't really an option. Most of my code has
3.
by nemequ1729 6y ago
I hadn't seen that post before, thanks. This doesn't quite apply to SIMDe; the problem that post is talking about is really at a higher level… whether it is faster to do a bunch of shuffles or use some scalar code. Once SIMDe is
4.
by nemequ1729 6y ago
> Not going to rewrite code I have already written, debugged and shipped. I wouldn't, either. At least unless you want a WASM/AltiVec/etc. version. But if you already have good implementations SIMDe probably won't he
5.
by nemequ1729 6y ago
I'm not aware of anything in the works for Intel, but RISC-V seems to be going in that direction. I'm hoping to start using SVE to implement AVX-512 and AVX in SIMDe soon.
6.
by nemequ1729 6y ago
It does include support for AVX-512, it's just still a work in progress. AVX-512 is enormous (IIRC ~ 4k functions), so it will be a while before it is fully supported. If you're targeting AVX-512 but don't have hardware that
7.
by nemequ1729 6y ago
Apart from the fact that you have to rewrite your code, the big disadvantage to something like this is that it's a bit slower. With SIMDe you're still free to use functions like `_mm_maddubs_epi16` and they'll be really fas
8.
by nemequ1729 6y ago
(Lead developer of SIMDe here.) It sounds like you actually know what you're doing, so in this case you're probably right, at least if all you do is compile your x86 code with SIMDe. That said, SIMDe also provides support for othe
9.
by nemequ1729 6y ago
I'm the lead developer of SIMDe. I wouldn't say that portability is the main focus. The first step is to get portable implementations up and running, but a huge number of functions have optimized implementations for NEON, AltiV