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

Add test for SYCL 2020 specialization constants #255

Merged

Conversation

AlexeySachkov
Copy link

No description provided.

@AlexeySachkov AlexeySachkov changed the title [WIP] Add tests for SYCL 2020 specialization constants Add test for SYCL 2020 specialization constants Apr 29, 2021
@AlexeySachkov AlexeySachkov marked this pull request as ready for review April 29, 2021 15:24
@AlexeySachkov AlexeySachkov requested a review from kbobrovs as a code owner April 29, 2021 15:24
kbobrovs
kbobrovs previously approved these changes Apr 29, 2021
// RUN: %GPU_RUN_PLACEHOLDER %t.out
// FIXME: ACC devices use emulation path, which is not yet supported
// FIXME: CUDA uses emulation path, which is not yet supported
// UNSUPPORTED: cuda

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+ UNSUPPORTED: acc?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have ACC_RUN_PLACEHOLDER, so it is not necessary


auto custom_type_acc =
custom_type_buffer.get_access<sycl::access::mode::read>();
const custom_type custom_type_ref;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: the default value of the custom_type_id coincides with default CPP (zeroes). the test could be strengthened by assigning custom_type_id some specific non-zero value to verify new SYCL2020 capabilities work for non-primitive types as well.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: the default value of the custom_type_id coincides with default CPP (zeroes).

It should have some non-zero default values, as I have its fields initialized: https://github.com/intel/llvm-test-suite/pull/255/files#diff-308baade624f8087060f981e03c24cffa77255b25f54deb6f7b7f1f6349a84afR16

return false;

return true;
}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For completeness, kernel_bundle-API based should also be tested. I guess these would be dozen extra lines of code. Can be addressed in a separate PR of course.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For completeness, kernel_bundle-API based should also be tested. I guess these would be dozen extra lines of code.

Sure, I definitively don't want to add those into the same test as it is huge enough already, but a separate file with such tests is needed for sure

@AlexeySachkov
Copy link
Author

@vladimirlaz, if I recall correctly, @kbobrovs approved this PR once. Since then only formatting changed - I suggest that we merge the PR and if there would be any additional feedback, I will apply it in a separate PR.

@vladimirlaz vladimirlaz merged commit 304433f into intel:intel May 17, 2021
aelovikov-intel pushed a commit to aelovikov-intel/llvm that referenced this pull request Mar 27, 2023
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