intel-intrinsics 1.0.13

The most practical D SIMD solution! Using SIMD intrinsics with Intel syntax with D.

To use this package, put the following dependency into your project's dependencies section:



Travis Status

The practical D SIMD solution. Use Intel intrinsics in D code.

This is a work in progress, please complain in the bugtracker.


import inteli.xmmintrin; // allows SSE1 intrinsics
import inteli.emmintrin; // allows SSE2 intrinsics

// distance between two points in 4D
float distance(float[4] a, float[4] b) nothrow @nogc
    __m128 va = _mm_loadu_ps(a.ptr);
    __m128 vb = _mm_loadu_ps(b.ptr);
    __m128 diffSquared = _mm_sub_ps(va, vb);
    diffSquared = _mm_mul_ps(diffSquared, diffSquared);
    __m128 sum = _mm_add_ps(diffSquared, _mm_srli_si128!8(diffSquared));
    sum = _mm_add_ps(sum, _mm_srli_si128!4(sum));
    return _mm_cvtss_f32(_mm_sqrt_ss(sum));
assert(distance([0, 2, 0, 0], [0, 0, 0, 0]) == 2);

Who is using it?

  • Pixel Perfect Engine is using intel-intrinsics for blitting images:
  • Dplug is using intel-intrinsics for biquad processing for a 10% speed gain over equivalent assembly:


Familiar syntax

Why Intel intrinsic syntax? Because it is more familiar to C++ programmers and there is a convenient online guide provided by Intel:

Without this guide it's much more difficult to write sizeable SIMD code.


LDC SIMD intrinsics are a moving target (, and you need a layer over it if you want to be safe.

We maintain that layer because we need it for our products.

Because those x86 intrinsics are internally converted to IR, they don't tie to a particular architecture. So you could target ARM one day and still get some speed-up.


For now only LDC is supported, but in the future the same set of intrinsics will work with DMD too. This is intended to be the most practical SIMD solution for D. Including an emulation layer for DMD 32-bit which doesn't have any SIMD capability right now.

Supported instructions set

  • SSE1
  • SSE2

The lack of AVX intrinsics is explained by the lack of raw speed gain with these instruction sets.

Important difference

When using the LDC compatibility layer (ie. when not using LDC), every implicit conversion of similarly-sized vectors should be done with a cast instead.

__m128i b = _mm_set1_epi32(42);
__m128 a = b;             // NO, only works in LDC
__m128 a = cast(__m128)b; // YES, works in all D compilers

This is because D does not allow implicit conversions, except magically in the compiler for real vector types.

1.0.13 2018-Oct-12
1.0.12 2018-Oct-11
1.0.11 2018-Jul-23
1.0.10 2018-Jul-12
1.0.9 2018-Jul-11
Show all 15 versions
Download Stats:
  • 20 downloads today

  • 214 downloads this week

  • 432 downloads this month

  • 3101 downloads total

Short URL: