-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Prohibit usage of <sycl/sycl.hpp>
in E2E tests
#13875
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
Depends on #13847, only the top commit should be reviewed under this PR. |
sycl/test-e2e/README.md
Outdated
headers only. However, the work of eliminating unnecessary dependencies between | ||
implementation header files is still in progress and the final set of these | ||
"fine-grained" includes that might be officially documented and suggested for | ||
customers to use isn't determined yet. Until then, code outside of this project |
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.
Should we bold "Until then, code outside of this project must keep using <sycl/sycl.hpp>
provided by the SYCL2020 specification." ?
It looks important for customers.
Fine-grained includes should be used instead for the benefits of compile-time. So far, the feature is still internal, customer code should continue using standard header files only. We can consider adding a Nightly workflow running E2E tests with extra compilation flag `-include sycl/sycl.hpp` if people think that would be important to have. I personally think that any potential discrepancies between full `sycl.hpp` and individual includes can be caught in compile-time and it should be enough to have tests in `sycl/test`.
4b6d2da
to
8827e52
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
Resource leak in |
@aelovikov-intel - sycl/test-e2e/no_sycl_hpp_in_e2e_tests.cpp has been seen failing in both pre-commit (#13888) and post-commit (#13359). |
My bad, I removed usage of |
intel#13875 made sycl/sycl.hpp include in E2E tests prohibited. However, LLVMIntrinsicLowering/sub_byte_bitreverse.cpp snuck in without this check. This commit fixes the includes in that test. Signed-off-by: Larsen, Steffen <[email protected]>
#13875 made sycl/sycl.hpp include in E2E tests prohibited. However, LLVMIntrinsicLowering/sub_byte_bitreverse.cpp snuck in without this check. This commit fixes the includes in that test. Signed-off-by: Larsen, Steffen <[email protected]>
Fine-grained includes should be used instead for the benefits of
compile-time. So far, the feature is still internal, customer code
should continue using standard header files only.
We can consider adding a Nightly workflow running E2E tests with extra
compilation flag
-include sycl/sycl.hpp
if people think that would beimportant to have. I personally think that any potential discrepancies
between full
sycl.hpp
and individual includes can be caught incompile-time and it should be enough to have tests in
sycl/test
.