This Intel® DPC++ Compatibility Tool minimizes code-migration time and assists in the migration of a developer's program that is written in CUDA* to a program written in Data Parallel C++ (DPC++) by generating DPC++ code for the developer wherever possible.
- Support for migration of CUDA* kernels, host and device API calls (for example, memory management, events, math, etc..) and library calls (cuBLAS*, cuSPARSE*, cuSolver*, cuRand*, Nvidia* Thrust*). Typically, 80%-90% of CUDA code migrates to DPC++ code by the tool.
- Warning messages are emitted to command line output and inlined into the generated code, when the code requires manual work to help you finish the application.
- Integration with Visual Studio* 2017 and 2019 on Windows* and Eclipse* on Linux* provides enhanced migration usability.
Please reference Intel® DPC++ Compatibility Tool System Requirements
How to use Intel® DPC++ Compatibility Tool
Please reference Getting Started Guide for Intel® DPC++ Compatibility Tool
Known Issues or Limitations
- Intel® DPC++ Compatibility Tool migrates memory copy API calls to USM sycl::queue.memcpy() by default. sycl::queue.memcpy() may not provide expected performance when run on DPC++ CPU device. To get better performance, you may try to replace cl::sycl::queue.memcpy() with parallel memcpy implemented by DPC++ kernel or try to migrate the code again with “--usm-level=none” passed to dpct.
- Intel® DPC++ Compatibility tool migrates thread synchronization API(s) to "sycl::nd_item::barrier()" without specifying parameters. You may improve performance by replacing "sycl::nd_item:: barrier()" with "sycl::nd_item:: barrier(sycl::access::fence_space::local_space)", if it is safe to do so, based on your algorithm analysis.
- If you migrate your Visual Studio CUDA project to DPC++ with the Visual Studio plugin of the Intel® DPC++ Compatibility Tool, please do not move the original CUDA project/source files to a different directory, while the migration is not complete. When you completed the migration and don’t need to use functionality of the Visual Studio plugin of the Intel® DPC++ Compatibility Tool, please, manually remove the migration.log file located in the migrated DPC++ project folder and then reopen the DPC++ project.
- If you use Intel® DPC++ Compatibility Tool to migrate project with compilation database (compile_commands.json) without specifying input files in command line, the Intel® DPC++ Compatibility Tool will try to migrate all source file(s) listed in compilation database together. If kernel function(s) with the same signature is redefined in several file(s) which are used to build different binary or library targets in original project, then the migration result may be wrong. The workaround is to migrate the source file(s) which are used to build one binary or library target together and not mix them with the source file(s) which are used to build the other binary or library target. You can specify the input file(s) to be migrated together in the command line of the Intel® DPC++ Compatibility Tool, or generate a set of the compilation databases by running “intercept-build make sub-target” with different sub-target each time and migrate source files with each compilation database.
Notices and Disclaimers
Intel technologies may require enabled hardware, software or service activation.
No product or component can be absolutely secure.
Your costs and results may vary.
© Intel Corporation. Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of others.
No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.
The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.
Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.