DPC++ Explicit SIMD API

This is a low-level API providing direct access to Intel GPU hardware features. ESIMD overview can be found here. Some terminology used in the API documentation: More...

Collaboration diagram for DPC++ Explicit SIMD API:

Modules
	Systolic Array APIs.
	APIs below are used to implement dot product accumulate systolic functions.
	ESIMD core.
	Core APIs defining main vector data types and their interfaces.
	Memory access API.
	ESIMD APIs to access memory via accessors, USM pointers, perform per-element atomic operations.
	ESIMD math operations.
	Defines math operations on ESIMD vector data types.
	Bit and mask manipulation APIs.
	Explicit conversions.
	Defines explicit conversions (with and without saturation), truncation etc. between ESIMD vector types.
	Raw send APIs.
	Implements the send instruction to send messages to variaous components of the Intel(R) processor graphics, as defined in the documentation at https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-icllp-vol02a-commandreference-instructions_2.pdf.
	Miscellaneous ESIMD convenience functions.

Detailed Description

This is a low-level API providing direct access to Intel GPU hardware features. ESIMD overview can be found here. Some terminology used in the API documentation:

• lane - (or "vector lane") Individual "lane" of input and output elements in a ESIMD vector operation, such that all lanes combined for the input and output vectors of the operation. Lane is indentified by an ordinal in the [0, N-1) range, where N is the size of the input/output vectors.
• mask - a vector of predicates which can be used to enable/disable execution of a vector operation over the correspondin lane. 0 predicate value disables execution, non-zero - enables.
• word - 2 bytes.
• dword ("double word") - 4 bytes.
• qword ("quad word") - 8 bytes.
• oword ("octal word") - 16 bytes.
• pixel A 4 byte-aligned contiguous 128-bit chunk of memory logically divided into 4 32-bit channels - R,G, B, A. Multiple pixels can be accessed by ESIMD APIs, with ability to enable/disable access to each channel for all pixels.

NOTES:

• API elements (macros, types, functions, etc.) starting with underscore _, as well as those in detail namespace, are never supposed to be used directly in the user code.