Intel® DPC++ Compatibility Tool Developer Guide and Reference

Developer Guide and Reference

  • 2022.2
  • 09/08/2022
  • Public Content
Contents

DPCT1003

Message

The migrated API does not return an error code, so
(*, 0)
 is inserted. You may need to rewrite this code.

Detailed Help

Typically, this happens because the CUDA* API returns an error code and then it is consumed by the program logic.
SYCL* uses exceptions to report errors and does not return the error code.
The Intel® DPC++ Compatibility Tool inserts a
(*, 0)
 operator, so that the resulting application can be compiled. This operator returns 0 and is inserted if the return code is expected by the program logic and the new API does not return it. You should review all such places in the code.

Suggestions to Fix

If in a DPC++ application you:
  • Do not need the code that consumes the error code, remove the code and the
    (*, 0)
     operator.
  • Need the code that consumes the error code, try to replace it with an exception handling code and use your logic in an exception handler.

Product and Performance Information

1

Performance varies by use, configuration and other factors. Learn more at www.Intel.com/PerformanceIndex.