Movatterモバイル変換


[0]ホーム

URL:


D Logo
Menu
Search

Language Reference

table of contents

Report a bug
If you spot a problem with this page, click here to create a Bugzilla issue.
Improve this page
Quickly fork, edit online, and submit a pull request for this page.Requires a signed-in GitHub account. This works well for small changes.If you'd like to make larger changes you may want to consider usinga local clone.

Vector Extensions

Contents
  1. core.simd
    1. Properties
    2. Conversions
    3. Accessing Individual Vector Elements
    4. Conditional Compilation
  2. X86 And X86_64 Vector Extension Implementation
    1. Vector Operation Intrinsics

CPUs often support specialized vector types and vector operations (a.k.a.media instructions). Vector types are a fixed array of floating or integer types, and vector operations operate simultaneously on them.

SpecializedVector types provide access to them.

TheVectorBaseType must be aStatic Array. TheVectorElementType is the unqualified element type of the static array. The dimension of the static array is the number of elements in the vector.

Implementation Defined: Which vector types are supported depends on the target. The implementation is expected to only support the vector types and operations that are implemented in the target's hardware.
Rationale: Emulating unsupported vector types and operations can exhibit such poor performance that the user is likely better off selecting a different algorithm than relying on emulation.
Best Practices: Use the declarations incore.simd instead of the languageVector grammar.

core.simd

Vector types and operations are introduced by importingcore.simd:

import core.simd;
Implementation Defined: These types and operations will be the ones defined for the architecture the compiler is targeting. If a particular CPU family has varying support for vector types, an additional runtime check may be necessary. The compiler does not emit runtime checks; those must be done by the programmer.
Implementation Defined: Depending on the target architecture, compiler flags may be required to activate support for SIMD types.

The types defined will all follow the naming convention:

typeNN
wheretype is the vector element type andNN is the number of those elements in the vector type. The type names will not be keywords.

Properties

Vector types have the property:

Vector Type Properties
PropertyDescription
.arrayReturns static array representation

Vectors support the following properties based on the vector element type. The value produced is that of a vector of the same type with each element set to the value corresponding to the property value for the element type.

Integral Vector Type Properties
PropertyDescription
.minminimum value
.maxmaximum value
Floating Point Vector Type Properties
PropertyDescription
.epsilonsmallest increment to the value 1
.infinityinfinity value
.maxlargest representable value that is not infinity
.min_normalsmallest representable value that is not 0
.nanNaN value

Conversions

Vector types of the same size (number_of_elements * size_of_element) can be implicitly converted among each other, this is done as a reinterpret cast (a type paint). Vector types can be cast to theirVectorBaseType.

Integers and floating point values can be implicitly converted to their vector equivalents:

int4 v = 7;v = 3 + v;// add 3 to each element in v

Accessing Individual Vector Elements

They cannot be accessed directly, but can be when converted to an array type:

int4 v;(cast(int*)&v)[3] = 2;// set 3rd element of the 4 int vector(cast(int[4])v)[3] = 2;// set 3rd element of the 4 int vectorv.array[3] = 2;// set 3rd element of the 4 int vectorv.ptr[3] = 2;// set 3rd element of the 4 int vector

Conditional Compilation

If vector extensions are implemented, theversion identifierD_SIMD is set.

Whether a type exists or not can be tested at compile time with anIsExpression:

staticif (is(typeNN))    ... yes, itis supported ...else    ... nope, use workaround ...

Whether a particular operation on a type is supported can be tested at compile time with:

float4 a,b;staticif (__traits(compiles, a+b))    ... yes, addis supportedfor float4 ...else    ... nope, use workaround ...

For runtime testing to see if certain vector instructions are available, see the functions incore.cpuid.

A typical workaround for unsupported vector operations would be to use array operations instead:

float4 a,b;staticif (__traits(compiles, a/b))    c = a / b;else    c[] = a[] / b[];

X86 And X86_64 Vector Extension Implementation

Implementation Defined:

The following describes the specific implementation of the vector types for the X86 and X86_64 architectures.

The vector extensions are currently implemented for the OS X 32 bit target, and all 64 bit targets.

core.simd defines the following types:

Vector Types
Type NameDescriptiongcc Equivalent
void1616 bytes of untyped datano equivalent
byte1616bytessigned char __attribute__((vector_size(16)))
ubyte1616ubytesunsigned char __attribute__((vector_size(16)))
short88shortsshort __attribute__((vector_size(16)))
ushort88ushortsushort __attribute__((vector_size(16)))
int44intsint __attribute__((vector_size(16)))
uint44uintsunsigned __attribute__((vector_size(16)))
long22longslong __attribute__((vector_size(16)))
ulong22ulongsunsigned long __attribute__((vector_size(16)))
float44floatsfloat __attribute__((vector_size(16)))
double22doublesdouble __attribute__((vector_size(16)))
void3232 bytes of untyped datano equivalent
byte3232bytessigned char __attribute__((vector_size(32)))
ubyte3232ubytesunsigned char __attribute__((vector_size(32)))
short1616shortsshort __attribute__((vector_size(32)))
ushort1616ushortsushort __attribute__((vector_size(32)))
int88intsint __attribute__((vector_size(32)))
uint88uintsunsigned __attribute__((vector_size(32)))
long44longslong __attribute__((vector_size(32)))
ulong44ulongsunsigned long __attribute__((vector_size(32)))
float88floatsfloat __attribute__((vector_size(32)))
double44doublesdouble __attribute__((vector_size(32)))
Note: for 32 bit gcc and clang, it'slong long instead oflong.
Supported 128-bit Vector Operators
Operatorvoid16byte16ubyte16short8ushort8int4uint4long2ulong2float4double2
=×××××××××××
+××××××××××
-××××××××××
*××××
/××
&××××××××
|××××××××
^××××××××
+=××××××××××
-=××××××××××
*=××××
/=××
&=××××××××
|=××××××××
^=××××××××
==××××××××××
!=××××××××××
<××××××××××
<=××××××××××
>=××××××××××
>××××××××××
unary~××××××××
unary+××××××××××
unary-××××××××××
Supported 256-bit Vector Operators
Operatorvoid32byte32ubyte32short16ushort16int8uint8long4ulong4float8double4
=×××××××××××
+××××××××××
-××××××××××
*××
/××
&××××××××
|××××××××
^××××××××
+=××××××××××
-=××××××××××
*=××
/=××
&=××××××××
|=××××××××
^=××××××××
==××××××××××
!=××××××××××
<××××××××××
<=××××××××××
>=××××××××××
>××××××××××
unary~××××××××
unary+××××××××××
unary-××××××××××

Operators not listed are not supported at all.

Vector Operation Intrinsics

Seecore.simd for the supported intrinsics.

Application Binary Interface
Better C
Copyright © 1999-2026 by theD Language Foundation | Page generated byDdoc on Sat Feb 21 00:13:46 2026

[8]ページ先頭

©2009-2026 Movatter.jp