Prevent user interface variables from containing a value of
type OpTypeBool (internal API issue 111).
diff --git a/extensions/ARB/ARB_gl_spirv.txt b/extensions/ARB/ARB_gl_spirv.txt
index 585ae36..221deb7 100644
--- a/extensions/ARB/ARB_gl_spirv.txt
+++ b/extensions/ARB/ARB_gl_spirv.txt
@@ -40,8 +40,8 @@
Version
- Last Modified Date: February 15, 2019
- Revision: 44
+ Last Modified Date: September 17, 2019
+ Revision: 45
Number
@@ -1150,6 +1150,10 @@
- For all entry points, the static function-call graph rooted at that
entry point must not contain cycles.
+ User declared input and output variables:
+ - Must not use OpTypeBool, either directly or as part of an aggregate.
+
+
A.spv.5 (Precision and Operation of SPIR-V Instructions)
The following rules apply to both single and double-precision floating
@@ -2170,6 +2174,11 @@
Rev. Date Author Changes
---- ----------- ------------ ---------------------------------
+ 45 17-Sep-2019 Jon Leech Add OpTypeBool constraint on user
+ interface variables in the
+ Validation Rules section (internal
+ API issue 111).
+
44 15-Feb-2019 apinheiro Added issue 28, about interaction with
ARB_get_program_binary (internal API issue 100)
43 15-Feb-2019 apinheiro Add uniform initializers reference and
