4a145dbf45
InputPatch parameters to patch constant functions were not using the internal (temporary) variable type. That could cause validation errors if the input patch had a mixture of builtins and user qualified members. This uses the entry point's internal form. There is currently a limitation: if an InputPatch is used in a PCF, it must also have appeared in the main entry point's parameter list. That is not a limitation of HLSL. Currently that situation is detected and an "implemented" error results. The limitation can be addressed, but isn't yet in the current form of the PR. |
||
---|---|---|
.. | ||
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.