EVE is a re-implementation of the old EVE SIMD library by Falcou et al. which for a while was named Boost.SIMD. It's a C++20 and onward implementation of a type based wrapper around SIMD extensions sets for most current architectures. It aims at showing how C++20 can be used to design and implement efficient, low level, high abstraction library suited for high performance.
It's a research project first and an open source library second. We reserve the right to change API and baseline compiler required until the first official 0.1 release. However, we'll try to minimize disruption. Semantic versioning will ensure API retro-compatibility if anything huge needs to change.
- Installing and using the library
- Your first SIMD code using EVE
- The complete set of EVE tutorials
- References Documentation
EVE is considered operational: it's usable, has a large feature set for a sensible amount of instruction sets but it's possible some values or performance issues may still remain. Don't hesitate to report any funky code-gen or bad optimizations so we can deliver the best performance around.
In term of SIMD extension sets, we actively supports (ie code is optimized and regularly tested) the following:
Full support with tests:
- Intel
- SSE2, SSSE3, SSE3, SSE4.1, SSE4.2
- AVX, AVX2, FMA3
- AVX512 in Skylake-AVX512 mode (F, CD, VL, DQ, BW)
- ARM
- NEON A32 (64 & 128 bits)
- NEON A64 (64 & 128 bits)
- ASIMD
- SVE with fixed sizes of 128, 256 and 512 bits registers.
Partial/In-progress support with minimal checks:
- PowerPC
- VMX
- VSX
We do not support ARM SVE with dynamic size nor GPGPU, this is the job for another tool.
EVE requires a C++ 20 compliant compiler. The main features from C++17/20 we require are:
- Concepts and requires
- Template lambdas
- Inline variables
- Non-Type Template Parameters
if constexpr- Functions from
<bits>
Here is the current minimal compiler version supported:
| Compiler | Version |
|---|---|
| g++ | 11 or above |
| clang++ | 13 or above |
| Visual Studio | TBD |
Visual Studio support is currently being added. Help on the front of setting up appveyor properly is also welcome.
-
Why C++20 ? Because we want to be able to use modern design components like Concepts, and later on, Modules. C++14 is for 2014. We fully know it may hinders adoption in some situation, but we're not running a race. We value proper design and API choice over complex retro-compatibility.
-
Why this instead of std::simd or any other libraries? EVE is a playground for testing proper design and implementation decisions for such libraries. Vc and its standard version are fine pieces of work but we aim at pushing the envelope in term of API and implementation without any standard restriction. We will try, however, to keep up with standard naming as much as possible.
-
Is this Boost.SIMD v42.69? Yes and no. This reimplementation is based on slightly different premises and some radical new ideas. All results exhibited by all our previous Boost.SIMD papers still hold and we'll try to improve upon.
-
I want to help! Good, we need tests on exotic configuration, maybe a stable PPC test machine. Write code, make it fail so we can improve for use cases we may have missed. Fork and hack away. We would also value input (even harsh ones) on how we use our CI infrastructure or how our CMake looks. We tried our best but those elements are complex all by themselves.
If you want to refer to EVE, you can currently use those papers (by order of preference in citation). A new, more up-to-date EVE specific journal paper is in the work atm.
- Modern Generative Programming for Optimizing Small Matrix-Vector Multiplication, Jules Penuchot, Joel Falcou, Amal Khabou in HPCS 2018
- Boost. simd: generic programming for portable simdization, Pierre Estérie, Joel Falcou, Mathias Gaunard, Jean-Thierry Lapresté, PACT 2012
- EVE, an object oriented SIMD library, Joel Falcou, Jocelyn Serot in Scalable Computing: Practice and Experience 6 (4)
Boost Software License
Copyright : EVE Project Contributors
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.