You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
The extension to compile SYCL code at runtime (#11985) only allows to compile SYCL device code at runtime, it does not specify an API to compile additional host code at runtime. Therefore, there is no need to generate the integration header during runtime compilation of SYCL code.
#15892, as a first step, removes some restrictions on free-function kernels that are needed for correct integration header support by omitting some tests and parts of the integration header.
As discussed in the PR, a next step would be to entirely stop emitting the integration header when compiling SYCL code at runtime.
Describe the solution you would like
No integration header generated when compiling SYCL code at runtime in runtime compilation mode.
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
The extension to compile SYCL code at runtime (#11985) only allows to compile SYCL device code at runtime, it does not specify an API to compile additional host code at runtime. Therefore, there is no need to generate the integration header during runtime compilation of SYCL code.
#15892, as a first step, removes some restrictions on free-function kernels that are needed for correct integration header support by omitting some tests and parts of the integration header.
As discussed in the PR, a next step would be to entirely stop emitting the integration header when compiling SYCL code at runtime.
Describe the solution you would like
No integration header generated when compiling SYCL code at runtime in runtime compilation mode.
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: