Recent generations of CPUs, and GPUs in particular, require data-parallel codes for full efficiency. Data parallelism requires that the same sequence of operations is applied to different input data. CPUs and GPUs can thus reduce the necessary hardware for instruction decoding and scheduling in favor of more arithmetic and logic units, which execute the same instructions synchronously. On CPU architectures this is implemented via SIMD registers and instructions. A single SIMD register can store N values and a single SIMD instruction can execute N operations on those values. On GPU architectures N threads run in perfect sync, fed by a single instruction decoder/scheduler. Each thread has local memory and a given index to calculate the offsets in memory for loads and stores.
Current C++ compilers can do automatic transformation of scalar codes to SIMD instructions (auto-vectorization). However, the compiler must reconstruct an intrinsic property of the algorithm that was lost when the developer wrote a purely scalar implementation in C++. Consequently, C++ compilers cannot vectorize any given code to its most efficient data-parallel variant. Especially larger data-parallel loops, spanning over multiple functions or even translation units, will often not be transformed into efficient SIMD code.
The Vc library provides the missing link. Its types enable explicitly stating data-parallel operations on multiple values. The parallelism is therefore added via the type system. Competing approaches state the parallelism via new control structures and consequently new semantics inside the body of these control structures.
Vc is a free software library to ease explicit vectorization of C++ code. It has an intuitive API and provides portability between different compilers and compiler versions as well as portability between different vector instruction sets. Thus an application written with Vc can be compiled for:
- AVX and AVX2
- SSE2 up to SSE4.2 or SSE4a
- Scalar
- MIC
- AVX-512 (in development)
- NEON (in development)
- NVIDIA GPUs / CUDA (in development)
Let's start from the code for calculating a 3D scalar product using builtin floats:
using Vec3D = std::array<float, 3>;
float scalar_product(Vec3D a, Vec3D b) {
return a[0] * b[0] + a[1] * b[1] + a[2] * b[2];
}Using Vc, we can easily vectorize the code using the float_v type:
using Vc::float_v
using Vec3D = std::array<float_v, 3>;
float_v scalar_product(Vec3D a, Vec3D b) {
return a[0] * b[0] + a[1] * b[1] + a[2] * b[2];
}The above will scale to 1, 4, 8, 16, etc. scalar products calculated in parallel, depending on the target hardware's capabilities.
For comparison, the same vectorization using Intel SSE intrinsics is more verbose and uses prefix notation (i.e. function calls):
using Vec3D = std::array<__m128, 3>;
__m128 scalar_product(Vec3D a, Vec3D b) {
return _mm_add_ps(_mm_add_ps(_mm_mul_ps(a[0], b[0]), _mm_mul_ps(a[1], b[1])),
_mm_mul_ps(a[2], b[2]));
}The above will neither scale to AVX, MIC, etc. nor is it portable to other SIMD ISAs.
cmake >= 3.0
C++11 Compiler:
- GCC >= 4.8.1
- clang >= 3.4
- ICC >= 15.0.3
- Visual Studio 2015 (64-bit target)
- Create a build directory:
$ mkdir build
$ cd build- Call cmake with the relevant options:
$ cmake -DCMAKE_INSTALL_PREFIX=/opt/Vc -DBUILD_TESTING=OFF <srcdir>- Build and install:
$ make -j16
$ make installThe documentation is generated via doxygen. You can build
the documentation by running doxygen in the doc subdirectory.
Alternatively, you can find nightly builds of the documentation at:
- M. Kretz, "Extending C++ for Explicit Data-Parallel Programming via SIMD Vector Types", Goethe University Frankfurt, Dissertation, 2015.
- M. Kretz and V. Lindenstruth, "Vc: A C++ library for explicit vectorization", Software: Practice and Experience, 2011.
- M. Kretz, "Efficient Use of Multi- and Many-Core Systems with Vectorization and Multithreading", University of Heidelberg, 2009.
Work on integrating the functionality of Vc in the C++ standard library.
A channel on the freenode IRC network is reserved for discussions on Vc: ##vc on freenode (via SSL)
Feel free to use the GitHub issue tracker for questions. Alternatively, there's a mailinglist for users of Vc
Vc is released under the terms of the 3-clause BSD license.