-
Notifications
You must be signed in to change notification settings - Fork 51
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
base: main
Are you sure you want to change the base?
Cooperative Vectors Test Plan #428
Conversation
@microsoft-github-policy-service agree company="NVIDIA" |
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? |
I added it to the cooperative vector proposal document as requested. |
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! |
Added more details on testing different shader stages in section 2.5. |
Added OOB tests to the plan and also updated InterlockedAdd to VectorAccumulate to align with new naming. |
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.