In the spec’s Vector-Matrix Operations section, it is unclear what the Vector column represents. As written, it appears to list the HLSL-facing vector type, but for Matrix x Vector Mul/MulAdd support, it seems more important to tabulate the types or interpretations that the operation actually supports natively, or via implementation-provided emulation.
In its current form, the table may imply direct support for the listed type even when a conversion step is required, and that conversion is not explicitly called out.
For comparison, the cooperative vector minimum support set used two separate columns: Input Type and Input Interpretation. That distinction was useful because Input Type described the HLSL type presented by the programmer, while Input Interpretation described the type actually consumed by the implementation, including cases where the implementation handled conversion to a non-native representation.
This section seems closer in meaning to Input Interpretation than to Input Type. It would also help to explicitly note in the surrounding commentary when support for a listed case may require an implicit conversion rather than reflecting native operand support in the multiply operation itself
In the spec’s Vector-Matrix Operations section, it is unclear what the
Vectorcolumn represents. As written, it appears to list the HLSL-facing vector type, but forMatrix x VectorMul/MulAddsupport, it seems more important to tabulate the types or interpretations that the operation actually supports natively, or via implementation-provided emulation.In its current form, the table may imply direct support for the listed type even when a conversion step is required, and that conversion is not explicitly called out.
For comparison, the cooperative vector minimum support set used two separate columns:
Input TypeandInput Interpretation. That distinction was useful becauseInput Typedescribed the HLSL type presented by the programmer, whileInput Interpretationdescribed the type actually consumed by the implementation, including cases where the implementation handled conversion to a non-native representation.This section seems closer in meaning to
Input Interpretationthan toInput Type. It would also help to explicitly note in the surrounding commentary when support for a listed case may require an implicit conversion rather than reflecting native operand support in the multiply operation itself