Skip to content
This repository was archived by the owner on Mar 28, 2023. It is now read-only.

[SYCL] Do not use cl_* types in some tests #1490

Merged

Conversation

AlexeySachkov
Copy link

cl_* types are defined by SYCL spec as interoperability interface with OpenCL. There is no need to use them in most of SYCL tests.

This change is mostly motivated by the fact that those cl_* type aliases were moved from sycl into sycl::opencl namespace: we simply want to avoid tests breakage when we align the implementation with the spec.

cl_* types are defined by SYCL spec as interoperability interface with
OpenCL. There is no need to use them in most of SYCL tests.

This change is mostly motivated by the fact that those cl_* type aliases
were moved from `sycl` into `sycl::opencl` namespace: we simply want to
avoid tests breakage when we align the implementation with the spec.
@AlexeySachkov AlexeySachkov requested review from a team as code owners January 5, 2023 16:11
@AlexeySachkov
Copy link
Author

@intel/dpcpp-tools-reviewers, @intel/llvm-reviewers-runtime, could you please take a look at this PR?

@AlexeySachkov AlexeySachkov merged commit 59b0171 into intel:intel Jan 27, 2023
myler pushed a commit to myler/llvm-test-suite that referenced this pull request Mar 22, 2023
`cl_*` types are defined by SYCL spec as interoperability interface with
OpenCL. There is no need to use them in most of SYCL tests.

This change is mostly motivated by the fact that those `cl_*` type aliases
were moved from `sycl` into `sycl::opencl` namespace: we simply want to
avoid tests breakage when we align the implementation with the spec.
aelovikov-intel pushed a commit to aelovikov-intel/llvm that referenced this pull request Mar 27, 2023
`cl_*` types are defined by SYCL spec as interoperability interface with
OpenCL. There is no need to use them in most of SYCL tests.

This change is mostly motivated by the fact that those `cl_*` type aliases
were moved from `sycl` into `sycl::opencl` namespace: we simply want to
avoid tests breakage when we align the implementation with the spec.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants