Visible to Intel only — GUID: GUID-FDC6BB6C-2DC7-43E2-848B-3DB2070EB387
Visible to Intel only — GUID: GUID-FDC6BB6C-2DC7-43E2-848B-3DB2070EB387
Before You Begin
Refer to Get Started with the Intel® DPC++ Compatibility Tool for installation and setup information.
Configure CLI Environment
Set up your CLI environment by running the setvars script located in the root of your toolkit installation.
On Linux* (sudo): source /opt/intel/oneapi/setvars.sh
On Linux (user): source ~/intel/oneapi/setvars.sh
On Windows*: C:\Program Files(x86)\Intel\oneAPI\setvars.bat
Samples
Several sample projects for Intel® DPC++ Compatibility Tool are available to explore the tool and familiarize yourself with how it functions.
To access the samples
use the oneapi-cli utility to select a sample from Intel® DPC++ Compatibility Tool category, or
download the samples from GitHub*.
For more information on how to download and access the samples, visit the Intel® oneAPI Base Toolkit Get Started Guides:
Sample Project |
Description |
---|---|
Vector Add
|
The Vector Add sample demonstrates how to migrate a simple program from CUDA* to SYCL*. Vector Add provides an easy way to verify that your development environment is setup correctly to use Intel® DPC++ Compatibility Tool. |
Folder Options
|
The Folder Options sample shows how to migrate more complex projects and to use options. |
Rodinia needleman-wunsch
|
The Rodinia needleman-wunsch sample demonstrates how to migrate a Make/CMake* project from CUDA to SYCL. |
Review the README file provided with each sample for more detailed information about the purpose and usage of the sample project.
Emitted Warnings
During the migration of the files Intel® DPC++ Compatibility Tool identifies places in the code that may require your attention to make the code SYCL compliant or correct.
Intel® DPC++ Compatibility Tool inserts comments into the generated source files which are displayed as warnings in the output. For example:
/path/to/file.hpp:26:1: warning: DPCT1003:0: Migrated API does not return error code. (*,0) is inserted. You may need to rewrite this code. // source code line for which warning was generated ^
For more details on what a particular warning means, see the Diagnostics Reference.