Skip to content

Cooperative Vectors Test Plan #428

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 2 commits into
base: main
Choose a base branch
from

Conversation

VladM1076
Copy link

@VladM1076 VladM1076 commented Mar 14, 2025

I have created a HLK/ExecTest test plan for the Cooperative Vectors feature and I am starting to work on its implementation.

Since the spec is still in flux, I have based it on the latest I am aware of and will keep it up to date as spec changes.

TODO: Update naming once spec is finalized.

@VladM1076
Copy link
Author

@microsoft-github-policy-service agree company="NVIDIA"

@damyanp
Copy link
Member

damyanp commented Mar 14, 2025

Thank you for getting this in! I'll probably not get a chance to review this properly until next week, but in the meantime would it be possible to add a link to this from the cooperative vector proposal document as well please?

@VladM1076
Copy link
Author

I added it to the cooperative vector proposal document as requested.
However since this is the HLSL test plan, wouldn't it be more appropriate in the vector-matrix operations proposal? Or just both?

@damyanp
Copy link
Member

damyanp commented Mar 14, 2025

I added it to the cooperative vector proposal document as requested. However since this is the HLSL test plan, wouldn't it be more appropriate in the vector-matrix operations proposal? Or just both?

The execution tests are really validating how the driver responds to the DXIL it receives. It's just that we write the tests in HLSL so we can use the compiler to generate the DXIL. That's much more convenient than hand-crafting DXIL!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

4 participants