Skip to content
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 SYCL 2020 accessor::value_type tests #395

Conversation

andylshort
Copy link

The accessor class's value_type member was updated recently to change its "const"-ness when in read-only mode (intel/llvm#7096) for SYCL 2020 compliance as defined in Section 4.7.6.9.1 The tests were not updated to reflect this change.

This patch specifically addresses the accessor_api_buffer_core test in the accessor_legacy directory and the error:

accessor_api_buffer_core - static assertion failed due to requirement 'std::is_same<const sycl::vec<int, 16>, sycl::vec<int, 16>>::value': value_type is of wrong type

In addition to the changes to accessor_api_common_all.h, it was necessary to resolve issues with accessor_api_image_common.h as there were tests in there for invalid targets. host_image, image, and image_array have been removed from the SYCL 2020 specification in favour of respectively specialised accessors. It was decided to simply remove these from the tests for that reason due to this being legacy testing.

Lamzed-Short, Andrew added 2 commits November 10, 2022 07:47
Section 4.7.6.9.1 changes value_type const-ness if accessor read-only.
Implementation was changed but test wasn't.
host_image, image_array, and image targets all removed form the specification
in favour of specialised accessors (https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#sec:what-changed-between)

These tests now pass. check_image_accessor_api_type commented out for now.
@CLAassistant
Copy link

CLAassistant commented Nov 11, 2022

CLA assistant check
All committers have signed the CLA.

@bader
Copy link
Contributor

bader commented Nov 13, 2022

@andylshort, please, fix code formatting.
Let me know if we need to uplift the dpcpp compiler to fix the compilation.

@andylshort
Copy link
Author

@bader Yes, the dpcpp compiler will need to be brought forward at least to commit intel/llvm@227614c where accessor::value_type was made SYCL 2020 compliant.

If there's any more issues with formatting, please do let me know!

@bader
Copy link
Contributor

bader commented Nov 16, 2022

Compiler version uplifting must be done from a local branch, so I pushed you changes + DPC++ version uplift to #398.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants