- Jan 03, 2019
-
-
David Neto authored
See #1642 Also updates SPIRV-Tools and SPIRV-Headers known_good.
-
- Dec 12, 2018
-
-
Jeff Bolz authored
Update to newest SPIRV-Tools. It checks the Vulkan rule that all resources must have a set and binding decoration, which many tests fail. So add code to set a default value of zero. Also disable PCH for Ninja builds.
-
- Dec 07, 2018
-
-
Alan Baker authored
* Changed unit tests to only record known the validation pass/fail status * errors are output as part of the failure message if the result is unexpected * can turn off validation for each test individually * Moved some SPV_KHR_vulkan_memory_model tests to be compiled for Vulkan 1.1
-
- Nov 02, 2018
-
-
Grigory Dzhavadyan authored
Consider the following code: layout(constant_id=0) const int Y = 1; layout(constant_id=1) const int Z = 2; layout(constant_id=3) const int X = Y + Z; Previously, it would produce SPIR-V decorations like this: Decorate 21(Y) SpecId 1 Decorate 22 SpecId 3 Decorate 33(Z) SpecId 0 This seems inaccurate, since the spec constant `X` that is dependent on the two others did not get a name in the SPIR-V decorations. This behavior may potentially negatively affect shader introspection capabilities. This change alters the behavior to always add a name, which results in the code above producing the following decorations: Decorate 21(Y) SpecId 1 Decorate 22(X) SpecId 3 Decorate 33(Z) SpecId 0
-
- Sep 11, 2018
-
-
John Kessenich authored
-
- Aug 23, 2018
-
-
John Kessenich authored
-
- Jun 05, 2018
-
-
John Kessenich authored
-
- Jun 04, 2018
-
-
John Kessenich authored
-
- May 25, 2018
-
-
Jeff Bolz authored
-
- Mar 07, 2018
-
-
John Kessenich authored
Now, version 5.* is all connected to making the uint type, which doesn't quite work. Generator versions 4 and 6 do not do this.
-
- Mar 06, 2018
-
-
John Kessenich authored
-