7f93d56ef2
Add support for Subpass Input proposal of issue #1069. Subpass input types are given as: layout(input_attachment_index = 1) SubpassInput<float4> subpass_f; layout(input_attachment_index = 2) SubpassInput<int4> subpass_i; layout(input_attachment_index = 3) SubpassInput<uint4> subpass_u; layout(input_attachment_index = 1) SubpassInputMS<float4> subpass_ms_f; layout(input_attachment_index = 2) SubpassInputMS<int4> subpass_ms_i; layout(input_attachment_index = 3) SubpassInputMS<uint4> subpass_ms_u; The input attachment may also be specified using attribute syntax: [[vk::input_attachment_index(7)]] SubpassInput subpass_2; The template type may be a shorter-than-vec4 vector, but currently user structs are not supported. (An unimplemented error will be issued). The load operations are methods on objects of the above type: float4 result = subpass_f.SubpassLoad(); int4 result = subpass_i.SubpassLoad(); uint4 result = subpass_u.SubpassLoad(); float4 result = subpass_ms_f.SubpassLoad(samp); int4 result = subpass_ms_i.SubpassLoad(samp); uint4 result = subpass_ms_u.SubpassLoad(samp); Additionally, the AST printer could not print EOpSubpass* nodes. Now it can. Fixes #1069 |
||
---|---|---|
.. | ||
AST.FromFile.cpp | ||
BuiltInResource.FromFile.cpp | ||
CMakeLists.txt | ||
Config.FromFile.cpp | ||
HexFloat.cpp | ||
Hlsl.FromFile.cpp | ||
Initializer.h | ||
Link.FromFile.cpp | ||
Link.FromFile.Vk.cpp | ||
main.cpp | ||
Pp.FromFile.cpp | ||
README.md | ||
Remap.FromFile.cpp | ||
Settings.cpp | ||
Settings.h | ||
Spv.FromFile.cpp | ||
TestFixture.cpp | ||
TestFixture.h |
Glslang Tests based on the Google Test Framework
This directory contains Google Test based test fixture and test cases for glslang.
Apart from typical unit tests, necessary utility methods are added into
the GlslangTests
fixture to provide the ability to do
file-based integration tests. Various *.FromFile.cpp
files lists names
of files containing input shader code in the Test/
directory. Utility
methods will load the input shader source, compile them, and compare with
the corresponding expected output in the Test/baseResults/
directory.
How to run the tests
Please make sure you have a copy of Google Test checked out under
the External
directory before building. After building, just run the
ctest
command or the gtests/glslangtests
binary in your build directory.
The gtests/glslangtests
binary also provides an --update-mode
command
line option, which, if supplied, will overwrite the golden files under
the Test/baseResults/
directory with real output from that invocation.
This serves as an easy way to update golden files.