Skip to content

[SYCL][Doc] Minor tweaks to SPV_INTEL_function_variants #19782

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

Open
wants to merge 3 commits into
base: sycl
Choose a base branch
from

Conversation

jdnk
Copy link
Contributor

@jdnk jdnk commented Aug 13, 2025

  • Fixes word count to match the consumer implementation
  • Allows multiple OpConditionalCopyINTEL condition operands to be true. During specialization, the first operand whose condition is true is selected.

@jdnk jdnk requested a review from a team as a code owner August 13, 2025 09:02
@@ -494,7 +494,7 @@ Add to Section 3.56.9, Function Instructions:
+
Make a copy of 'Operand X' if 'Condition X' is *true*.

From all 'Condition X'-'Operand X' pairs, 'exactly' one 'Condition X' must be *true*. Consequently, at least one 'Condition X'-'Operand X' pair must be present.
From all 'Condition X'-'Operand X' pairs, at least one 'Condition X' must be *true*. Consequently, at least one 'Condition X'-'Operand X' pair must be present.
Copy link
Contributor

Choose a reason for hiding this comment

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

In the uses cases I can think of, setting more than one Condition X to true would indicate that something went wrong. What is the rationale for allowing this and arbitrarily using the first condition? Should we instead say this is not allowed and add a validation check?

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