Execution tests for the new linear algebra apis are needed to verify correct support on all platforms.
The current smoke tests target the internal compiler API but now that its easier to target the header API directly that may be preferred.
The ExecTests must be written to cover each builtin across the various dimensions of its parameters taking care to assert specific edge cases.
Some examples of expectations:
- Matrix params/returns should be tested with various types/dimensions/uses/scopes in both square and non-square shapes
- integer type should explore full valid ranges
- sources/destinations for serialized/deseralized matrix data should vary over size/layout/type/offset similar type things
- out of bounds behavior should be explored
- vector params should explore types/sizes as permitted per op
Some notion of runtime querying will be needed for most of the tests as the feature allows hardware to opt out of a lot of subfeatures.
CoopVec Exec Tests may be a good place to source inspiration or data sets from!
Execution tests for the new linear algebra apis are needed to verify correct support on all platforms.
The current smoke tests target the internal compiler API but now that its easier to target the header API directly that may be preferred.
The ExecTests must be written to cover each builtin across the various dimensions of its parameters taking care to assert specific edge cases.
Some examples of expectations:
Some notion of runtime querying will be needed for most of the tests as the feature allows hardware to opt out of a lot of subfeatures.
CoopVec Exec Tests may be a good place to source inspiration or data sets from!