5 Commits

Author	SHA1	Message	Date
Ehsan Nasiri	f2867d7485	The Signedness in OpTypeInt must always be 0. ... When Kernel capability is used, The Signedness in OpTypeInt must always be 0. Fixes issue #492.	2017-02-10 12:21:16 -05:00
Ehsan Nasiri	1c11c8690f	Validation of OpEntryPoint usage. ... According to the SPIRV Spec (2.16.1): * There is at least one OpEntryPoint instruction, unless the Linkage capability is being used. * No function can be targeted by both an OpEntryPoint instruction and an OpFunctionCall instruction. Also updated unit tests to includ OpEntryPoint.	2017-01-13 16:15:11 -05:00
Ehsan Nasiri	8c414eb579	Adding validation code for OpTypeStruct. ... According to the Data Rules section of 2.16.1. Universal Validation Rules of the SPIR-V Spec: Forward reference operands in an OpTypeStruct * must be later declared with OpTypePointer * the type pointed to must be an OpTypeStruct * had an earlier OpTypeForwardPointer forward reference to the same <id>	2016-11-16 16:41:56 -05:00
Ehsan Nasiri	d0620061c7	Adding validation code for more data rules. ... These rules are under "Data Rules" in 2.16.1 (Universal Validation Rules) part of the SPIR-V 1.1 Specification document: * Scalar floating-point types can be parameterized only as 32 bit, plus any additional sizes enabled by capabilities. * Scalar integer types can be parameterized only as 32 bit, plus any additional sizes enabled by capabilities. * Vector types can only be parameterized with numerical types or the OpTypeBool type. * Matrix types can only be parameterized with floating-point types. * Matrix types can only be parameterized as having only 2, 3, or 4 columns. * Specialization constants (see Specialization) are limited to integers, Booleans, floating-point numbers, and vectors of these.	2016-11-15 13:38:39 -05:00
Lei Zhang	2881fe958f	Rename validation tests to comply with Google style guide.	2016-11-08 17:19:11 -08:00