-
Notifications
You must be signed in to change notification settings - Fork 150
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
Use of sycl::half, with CL/sycl.hpp SYCL header included #149
Comments
@sbalint98 Thanks for bringing up this issue. I wonder if option 2 is a viable option. Did you get a chance to try it with hipSYCL and DPC++? |
I'll have a look at option two and open a PR if it works |
It looks to me that the If you can confirm that the EDIT: |
Any chance you can send your branch so I can take a quick look before opening a PR? |
I looked at the 2021.4 release and indeed could not locate sycl/sycl.hpp. Sorry for the confusion with my comment. We can exclude option 2 as you suggested. |
Sure, have a look at this branch: https://github.com/sbalint98/oneMKL/tree/fix-qualification-ver2 |
@sbalint98 After looking through your branch, I would actually prefer a hipSYCL specific solution like in option 3. Could we bring that one back? Sorry for the inconvenience. |
No problem, added the change as requested to the PR #144 |
Closing issue. It is handled with option 3. |
In #143, the
half
data types were replaced withsycl::half
, while including theCL/sycl.hpp
SYCL header. According to the SYCL specification section 4.3, when that header is included all SYCL types should exist inside the::cl::sycl
namespace.Unfortunately, this change also breaks compilation with hipSYCL, since
sycl::half
is not defined. In order to solve this problem I see three possible solutions:::cl::sycl
namespace for half as well::sycl
namespace in case of all SYCL types, and include thesycl/sycl.hpp
header instead ofCL/sycl.hpp
I think the most consistent and least error-prone solution would be the first one. Can you give some feedback on what would be the preferred solution?
The text was updated successfully, but these errors were encountered: