Diagnostics Reference¶
This topic gives you all of the diagnostic reference numbers, messages, detailed help, and suggestion to fix your errors.
ID |
Message |
---|---|
An error handling |
|
The statement could not be removed. See the details in the resulting file comments. |
|
A special case error handling |
|
The migrated API does not return an error code, so |
|
Compatible DPC++ code could not be generated. |
|
The SYCL device version is different from CUDA Compute Compatibility. You may need to rewrite this code. |
|
DPC++ does not provide a standard API to differentiate between integrated/discrete GPU devices. |
|
Migration of this API is not supported by the Intel® DPC++ Compatibility Tool. |
|
The clock function is not defined in DPC++. This is a hardware-specific feature. Consult with your hardware vendor to find a replacement. |
|
SYCL uses exceptions to report errors and does not use error codes. The original code was commented out and a warning string was inserted. You may need to rewrite this code. |
|
SYCL uses exceptions to report errors and does not use error codes. The call was replaced with 0. You may need to rewrite this code. |
|
The tool detected overloaded operators for built-in vector types, which may conflict with the SYCL 1.2.1 standard operators (see 4.10.2.1 Vec interface). The tool inserted a namespace to avoid the conflict. Use SYCL 1.2.1 standard operators instead. |
|
Detected a kernel execution time measurement pattern and generated an initial code for time measurements in SYCL. You can change the way time is measured depending on your requirements. |
|
The rounding mode could not be specified and the generated code may have different precision than the original code. Verify the correctness. The SYCL math built-in functions rounding mode is aligned with the OpenCL™ C 1.2 standard. |
|
The flag/priority options are not supported for SYCL queues; the output parameter(s) are set to 0. |
|
The output requires adjustment. |
|
The <API name> was not migrated, because parameter(s) <parameter name a> and/or <parameter name b> could not be evaluated, or because <parameter name a> is not equal to <parameter name b>. Rewrite this code manually. |
|
The <DPC++ API name> call is used instead of the <CUDA API name> call. These two calls do not provide the same functionality. Check the potential precision and/or performance issues for the generated code. |
|
The <API name> was migrated, but the generated code performance may be sub-optimal due to the following reasons:
|
|
The |
|
The migration of <api name>, if it is called from |
|
Migration of |
|
There is no exact match between the |
|
The DPC++ sub-group does not support mask options for <api name>. |
|
The original code returned the error code that was further consumed by the program logic. This original code was replaced with 0. You may need to rewrite the program logic consuming the error code. |
|
The SYCL queue is created ignoring the flag/priority options. |
|
The call to <API name> was removed, because <reason>. The reason can be:
|
|
The call to <API name> was replaced with 0, because <reason>. The reason can be:
|
|
The |
|
DPC++ currently does not support getting device resource limits. The output parameter(s) are set to 0. |
|
DPC++ currently does not support inter-process communication (IPC) operations. You may need to rewrite the code. |
|
DPC++ currently does not support memory access across peer devices. The output parameter(s) are set 0. |
|
A different random number generator is used. You may need to adjust the code. |
|
The migrated code uses a basic Sobol generator. Initialize the |
|
The migrated API does not return an error code. 0 is returned in the lambda. You may need to rewrite this code. |
|
All DPC++ devices can be used by the host to submit tasks. You may need to adjust this code. |
|
The type |
|
Rewrite this code using |
|
When the kernel function name is used as a macro argument, the migration result may be incorrect. You need to verify the definition of the macro. |
|
The generated code assumes that |
|
Use |
|
SYCL uses exceptions to report errors, it does not use error codes. 0 is used instead of an error code in an if/while/do/for/switch/return statement. You may need to rewrite this code. |
|
The size of the arguments passed to the SYCL kernel exceeds the minimum size
limit (1024) for a non-custom SYCL device. You can get the hardware argument size
limit by querying |
|
The version-related API is different in SYCL. An initial code was generated, but you need to adjust it. |
|
|
|
Migration is only supported for this API for the general sparse matrix type. You may need to adjust the code. |
|
The
|
|
The meaning of |
|
The original value |
|
The workgroup size passed to the SYCL kernel may exceed the limit. To get the
device limit, query |
|
The template argument of the |
|
DPC++ does not support the device property that would be functionally compatible
with |
|
DPC++ does not support the member access for a volatile qualified vector type. The volatile qualifier was removed. You may need to rewrite the code. |
|
Migration of device assembly code is not supported. |
|
The type of variable |
|
Vector types with size 1 are migrated to the corresponding fundamental types, which cannot be inherited. You need to rewrite the code. |
|
The Intel® DPC++ Compatibility Tool did not detect the variable |
|
Variable |
|
|
|
SYCL only supports 4-channel image format. Adjust the code. |
|
SYCL range can only be a 1D, 2D, or 3D vector. Adjust the code. |
|
Call to |
|
SYCL Image doesn’t support normalized read mode. |
|
Advice parameter is device-defined. You may need to adjust it. |
|
Migrated |
|
Consider replacing |
|
Input/Output distance are migrated to FWD/BWD_DISTANCE. You may need to update the code manually. |
|
The |
|
The value of |
|
The argument |
|
|
|
The placement of the FFT computational function could not be deduced, so it is assumed out-of-place. You may need to adjust the code. |
|
DPC++ currently does not support getting the available memory on the current device. You may need to adjust the code. |
|
The field values of parameter |
|
The SYCL Image class does not support some of the flags used in the original code. Unsupported flags were ignored. Data read from SYCL Image could not be normalized as specified in the original code. |
|
Migration of cuFFT calls may be incorrect and require review. |
|
The device attribute was not recognized by the Intel(R) DPC++ Compatibility Tool. You may need to adjust the code. |
|
|
|
Consider replacing |
|
Replace “Placeholder” with the file path of the dynamic library. |
|
Variadic functions cannot be called in a SYCL kernel or by functions called by the kernel. You may need to adjust the code. |
|
The generated code assumes that |
|
The type |