-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] populate PI (and direct SYCL RT to PI) #259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Review the commit |
1968626
to
ceef833
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
A few minor comments.
@@ -13,6 +13,7 @@ | |||
#include <CL/sycl/context.hpp> | |||
#include <CL/sycl/detail/aligned_allocator.hpp> | |||
#include <CL/sycl/detail/common.hpp> | |||
#include <CL/sycl/detail/pi.hpp> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, keep includes sorted.
Usually these types of issues are handled automatically by clang-format tool.
Signed-off-by: Sergey V Maslov <[email protected]>
…/device stuff. Signed-off-by: Sergey V Maslov <[email protected]>
Signed-off-by: Sergey V Maslov <[email protected]>
Signed-off-by: Sergey V Maslov <[email protected]>
#else | ||
Queue = clCreateCommandQueue(ClContext, m_Device.get(), | ||
CreationFlags, &Error); | ||
// TODO: do we really need this old interface into PI and here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. This should be handled by OpenCL plugin. The plug-in should know where to lower piQueueCreate
to clCreateCommandQueueWithProperties
or to clCreateCommandQueue
.
This incremental change on top of PI infrastructure being added in #222. It turns all of SYCL RT OpenCL calls into PI. For the time being PI implementation is still directly the OpenCL one (in pi_opencl.*), and the next step will be to run OpenCL through the PI.