Verbose Message Catalogue¶
The following catalogue lists verbose messages, explanations, and additional information for: primitive creation and dispatch checks for primitive implementations; and implementation failures that occur during engine/memory object creation.
Primitive Creation/Dispatching¶
VERBOSE MESSAGE |
SUBSTRING |
PRIMITIVE |
EXPLANATION |
---|---|---|---|
Bad/Invalid Arguments |
|||
|
all |
Bad or invalid algorithm |
|
|
all |
Incorrect propagation kind |
|
|
|
all |
Invalid parameter passed for the initialization of the primitive descriptor. Example : For the |
|
all |
A NULL pointer argument exception for the primitive methods. |
|
|
all |
Bad or unsupported flags specified for the initialization of the primitive descriptor |
|
Unsupported Arguments/Parameters |
|||
|
all |
Primitive implementation does not support the current ISA. This typically results in the dispatching to the next best supporting implementation for the ISA. |
|
|
all |
Tensor data type is not supported for the current implementation of the primitive. Depending on the primitive, this may correspond to the source, weights, bias or destination tensors. |
|
|
all |
Datatype combination for source, weights, bias or destination tensors is not supported for the current primitive implementation. |
|
|
all |
Bad or unsupported attributes |
|
|
all |
Unsupported post-ops configuration |
|
|
all |
Unsupported scales configuration specified for the primitive attributes |
|
|
all |
Unsupported zero-point configuration specified for the primitive attributes |
|
|
compute-based primitives |
Unsupported bias data configuration specified for the descriptors. |
|
|
|
Current primitive implementation does not support sparse data operations. |
|
|
all |
Unsupported format tag |
|
|
|
all |
Unsupported format tag |
|
all |
Unsupported format kind |
|
|
all |
Current implementation does not support processing runtime-specified shapes and strides using |
|
Tensor Operations |
|||
|
|
all |
Empty tensor passed as data to the primitive. Depending on the primitive, this may correspond to the source, weights or destination tensors. |
|
|
all |
Tensor data has bad or invalid number of dimensions for the current primitive operation. Example : The |
|
|
all |
Tensor |
|
|
all |
Tensors |
|
|
all |
One of the dimensions of tensor |
|
|
all |
Tensors |
|
|
all |
Tensors |
Unsupported Combinations |
|||
|
all |
(self-explanatory) |
|
|
all |
(self-explanatory) |
|
|
all |
(self-explanatory) |
|
|
|
all |
Tensors |
Implementation Heuristics/Features |
|||
|
|
all |
Current implementation is skipped because it does not support the specified feature for the primitive operation. |
|
|
all |
Current implementation is skipped because the selected device does not support the specified feature for primitive operation. |
|
|
all |
Current implementation is skipped because of a padding inconsistency or unsupported feature related to padding. |
|
|
all |
Implementation skipped due to specified heuristic. |
|
|
all |
Current implementation is skipped because of the specified inconsistency or implementation heuristic related to blocking. |
Primitive-Specific Messages |
|||
|
|
|
Implementation skipped due to specified heuristic related to 1x1 convolution. |
|
|
|
I/O dimension offsets do not fit into the specified datatype range for the kernel implementation. |
|
|
Implementation skipped because the current data layout/shapes exceeds the range supported by the current implementation. |
|
|
|
Alpha and beta parameters are not properly set for the elementwise algorithm. |
|
|
|
Heuristic to skip current implementation for large tensor shapes for better performance. |
|
|
|
Current implementation for the primitive does not process non-trivial stride values. |
|
|
|
Floating-point math mode is not supported by the current primitive implementation. |
|
|
|
Heuristic to skip current implementation for small tensor shapes for better performance. |
|
|
|
Specified GeMM format is incompatible with the current primitive implementation. |
|
|
|
|
The data layout for the source/destination tensor is not supported by the current implementation. |
|
|
Bad or invalid axis specified for softmax/shuffle operation. |
|
|
|
Unsupported architecture for specified device-type. Typically encountered when current GPU device does not support the primitive. |
|
Miscellaneous |
|||
|
|
all |
Descriptor initialization for the nested primitive implementation was unsuccessful. |
|
|
all |
Descriptor initialization for the primitive or memory object was unsuccessful. |
|
all |
Bad or invalid accumulation mode specified for primitive attribute |
|
|
|
all |
Bad or unsupported flags specified for the memory descriptor |
|
all |
(self-explanatory) |
|
|
all |
(self-explanatory) |
|
|
all |
Workspace descriptor initialization was unsuccessful during primitive creation. |
|
|
|
all |
The data type for the tensor/data processed by the primitive is invalid. Example : This is encountered when an undefined data type |
|
all |
failed to run application in the deterministic mode . |
|
|
all |
(self-explanatory) |
|
|
|
all |
(self-explanatory) |
Engine Creation¶
VERBOSE MESSAGE |
SUBSTRING |
ENGINE |
EXPLANATION |
---|---|---|---|
|
all |
Invalid value for |
|
|
|
all |
Device of type |
|
|
all |
No device of type |
|
|
all |
Queried index is out-of-range for device of type |
|
all |
(self-explanatory) |
|
|
|
|
Unsupported device platform encountered during engine creation. |
|
|
all |
Engine creation was unsuccessful for the specified device index and kind. |
|
|
(self-explanatory) |
|
|
all |
Experimental profiling ( ONEDNN_EXPERIMENTAL_PROFILING ) is not enabled for the application. |