Say how the validator checks universal limits

Indicate it's future work to allow parameterization of those
limits.
This commit is contained in:
David Neto 2016-11-30 15:48:39 -05:00
parent 3c8bc80e3a
commit 5f2d40915e
2 changed files with 13 additions and 0 deletions

View File

@ -4,6 +4,12 @@ v2016.6-dev 2016-09-16
- Published the C++ interface for assembling, disassembling, validation, and
optimization.
- Support SPV_KHR_shader_draw_parameters in assembler, disassembler, parser.
- Validator has increased coverage:
- Checks "Data rules" in Universal Validation Rules, section 2.16.1
- WIP: Universal Limits.
- The minimum mandated upper bounds are checked.
- TODO: Parameterize the validator to allow larger limits accepted by
a more than minimally capable implementation.
- Fixes issues:
#429: Validator: Allow OpTypeForwardPointer and OpTypeStruct to reference
undefined IDs

View File

@ -56,6 +56,13 @@ See [`syntax.md`](syntax.md) for the assembly language syntax.
### Validator
*Warning:* The validator is incomplete.
Check the [CHANGES](CHANGES) file for reports on progress.
*Note*: The validator checks some Universal Limits, from section 2.17 of the SPIR-V spec.
The validator will fail on a module that exceeds those minimum upper bound limits.
It is future work to parameterize the validator to allow larger
limits accepted by a more than minimally capable SPIR-V consumer.
### Optimizer