-
Notifications
You must be signed in to change notification settings - Fork 68
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
Fix contradiction with context constructors #628
base: main
Are you sure you want to change the base?
Conversation
Retarget to |
The context constructor overloads in the `context` synopsis did not match the description in the text of the specification. We decided that the overloads in the synopsis were what we intended, so change the text to match. We also discovered that two constructor overloads taking a `platform` argument were present in SYCL 1.2.1 and were inadvertently dropped from the SYCL 2020 specification. Add them back. Clarify the behavior of the constructors when the set of devices is empty. We decided that this should throw an exception, which is consistent with OpenCL's `clCreateContext`. Closes KhronosGroup#470 Closes KhronosGroup#474
29cbcdc
to
a4543c6
Compare
---- | ||
explicit context(const device& dev, async_handler asyncHandler = {}) | ||
explicit context(const platform &plt, const property_list &propList = {}) |
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.
Have we changed the coding style about *
and &
? 🤔
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.
Oops, thanks for catching this. Fixed in 2887f9c.
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.
Thanks!
For my own benefit, this Intel internal tracker requests the CTS coverage for this PR: CMPLRLLVM-65051 |
The context constructor overloads in the
context
synopsis did not match the description in the text of the specification. We decided that the overloads in the synopsis were what we intended, so change the text to match.We also discovered that two constructor overloads taking a
platform
argument were present in SYCL 1.2.1 and were inadvertently dropped from the SYCL 2020 specification. Add them back.Clarify the behavior of the constructors when the set of devices is empty. We decided that this should throw an exception, which is consistent with OpenCL's
clCreateContext
.Closes #470
Closes #474