DPCT1103

Intel® DPC++ Compatibility Tool Developer Guide and Reference

Download PDF

ID 768918

Date 7/13/2023

Version

Public

A newer version of this document is available. Customers should click here to go to the newest version.

Visible to Intel only — GUID: GUID-10DA65C8-F84C-4C84-B972-AC0821271E6C

View Details

DPCT1103

Message

<expression text> should be a dynamic library. The dynamic library should supply wrapped kernel functions.

Detailed Help

The CUDA* application expects <expression text> to be the name of a CUDA module. The user should ensure that the CUDA code that generated the CUDA module is migrated to SYCL* code and compiled to generate a kernel library.

Suggestions to Fix

The user should find the module source files that are used to make the CUDA module and migrate them to SYCL using the --extra-arg=-ptx option of Intel® DPC++ Compatibility Tool to generate wrapped kernel functions:

dpct <module source file(s)> --extra-arg=--ptx

The migrated module source file(s) should be compiled to make a kernel library.

On Linux*:

icpx -fsycl <migrated module source file(s)> -fPIC -shared -o <kernel library filename>

On Windows*:

icpx -fsycl <migrated module source file(s)> -shared -o <kernel library filename>

The <kernel library filename> should be chosen so that <expression text> will have the same filename at runtime. For the following example, <kernel library filename> should be set to library.so.

For example, this original CUDA code:

  char *ptxFile = "module.ptx";
  cuModuleLoad(&module, ptxFile);

results in the following migrated SYCL code:

  char *ptxFile = "module.ptx";
  module = dpct::load_kernel_library(ptxFile);

which is rewritten to:

  char *libraryFile = "library.so";
  module = dpct::load_kernel_library(libraryFile);

Select Your Language

Using Intel.com Search

Quick Links

Recent Searches

Advanced Search

Only search in

Intel® DPC++ Compatibility Tool Developer Guide and Reference

DPCT1103

Message

Detailed Help

Suggestions to Fix