Visible to Intel only — GUID: GUID-3925B25D-E581-4127-B202-1F01EE003A66
Visible to Intel only — GUID: GUID-3925B25D-E581-4127-B202-1F01EE003A66
Migrate a Project on Windows*
Use the Command Line
Intel® DPC++ Compatibility Tool can be invoked at the command line.
If your project uses Microsoft Visual Studio*, you can use the --vcxprojfile option to point to the project that requires migration. Intel® DPC++ Compatibility Tool will migrate the files you provided as input files.
The following steps show how to migrate the Vector Add sample using Intel® DPC++ Compatibility Tool:
Get the Vector Add sample:
Use the oneapi-cli utility to select the sample from the Intel® DPC++ Compatibility Tool category.
Download the sample from GitHub*
Navigate to the root of the Vector Add sample.
The sample contains a single CUDA* file, vector_add.cu, located in the src folder.
From the root folder of the sample project, run Intel® DPC++ Compatibility Tool.
To migrate the single file src\vector_add.cu, which is part of vector-add.vcxproj, run:
dpct --vcxprojfile=vector-add.vcxproj --in-root=./ --out-root=output_proj src\vector_add.cu
Alternately, to migrate all relevant files found by the tool in vector-add.vcxproj, run:
dpct --vcxprojfile=vector-add.vcxproj --in-root=./ --out-root=output_proj
In both cases, the result of the migration is sent to the output_proj folder.
Use Microsoft Visual Studio*
You can use Intel® DPC++ Compatibility Tool within the Microsoft Visual Studio IDE to migrate your project to a SYCL project.
Step 1: Select an Existing Project and Start Migration
To select an existing project in Microsoft Visual Studio and start migration:
From the Extensions menu, select Browse Intel® oneAPI Samples
Select Rodinia NW DPCT from the Intel® DPC++ Compatibility Tool category.
Select the Project menu >Migrate Project to DPC++.
In the Select Project to Migrate dialog, click Browse.
Select the directory and the existing project file in the Open dialog.
Select the Configuration and Platform to migrate.
Click OK.
Step 2: Specify the Migration Configuration
After selecting an existing project, you will see the Migration Configuration dialog. These configurations have default values. You can specify the configurations, including the new project file name and directory, the --in-root argument, and the additional options for the migration.
The command line area is read-only and shows the command line that will be used to migrate the project.
The migration starts once you click OK.
Step 3: Verify the Source for Correctness
Verify the migration of the source code that uses variables declared using preprocessor directives. Inspect the migrated source code, address any DPCT warnings generated, and verify correctness of the new program.
Review Emitted Warnings for additional information about inserted warnings and comments.
For the most accurate and detailed instructions on addressing warnings, see the Addressing Warnings in the Migrated Code section of the sample README files.
Step 4: Check the Detailed Diagnostic Messages
To learn more about a diagnostic message, click the Help hyperlink in the Actions column, which is located in the table in the Intel® DPC++ Compatibility Tool view. Details about why the diagnostic message is generated and information on how to fix the issue are shown.
Specifying Options
You can set your preferences for Intel® DPC++ Compatibility Tool within Microsoft Visual Studio:
To always show warnings after migration:
Select Tools > Options > Intel® DPC++ Compatibility Tool > General.
Select True (the default) for the Always show warnings after migration option.
Click OK.
To enable opening code side-by-side:
Select Tools > Options > Intel® DPC++ Compatibility Tool > General.
Select True (the default) for the Enable opening code side-by-side option.
Click OK.
To select a version of the tool:
If you have multiple versions of Intel® DPC++ Compatibility Tool installed, you can select which version to use.
Select Tools > Options > Intel® DPC++ Compatibility Tool > Tools.
Use the drop-down menu from the step above to select the appropriate version of the tool.
Select the default options (optional).
Click OK.