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

[Spec change] Clarify vec::as behavior #1043

Closed
sycl-issue-bot bot opened this issue Feb 13, 2025 · 1 comment
Closed

[Spec change] Clarify vec::as behavior #1043

sycl-issue-bot bot opened this issue Feb 13, 2025 · 1 comment

Comments

@sycl-issue-bot
Copy link

Please review whether KhronosGroup/SYCL-Docs#724 by @Pennycook requires any changes to the CTS.

If changes are required: Open a new PR addressing the changes and link it to this issue.
If no changes are required: Close this issue and proceed with the spec PR.

@Pennycook
Copy link
Contributor

The issue that originally spotted this problem (KhronosGroup/SYCL-Docs#455) noted that this was identified via the CTS, and that invalid uses of vec::as<bool> had already been removed from the CTS. As such, I don't think any additional CTS changes are required.

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

No branches or pull requests

1 participant