Address several outstanding LinAlg open items#250
Open
jenatali wants to merge 1 commit into
Open
Conversation
vdwtanner
approved these changes
Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses outstanding issues:
MATRIX_CONSTRUCTION_SUPPORTtakes a singleShapeinput +BOOLoutput.Additional issues heard offline but not filed as an issue: Customers like Vulkan's "show me everything" model, so in addition to the "does this work" question at the API, I've added a full table enumeration API and DDI. The driver may choose to just expose the table to the runtime, and the runtime can search it to answer the more granular support queries, or the driver may choose to expose both kinds of queries. This can make sense if the number of natively supported cases is large (e.g. WARP with SSE2 through AVX512 will produce a very large table, but answering support questions is easy).
The DDI is explicitly documented since it's less obvious how closely it'll map exactly to the API.