8c49d15fbf
This change strips a few features similar to GLSLANG_WEB but doesn't remove every detail like the latter. It also hardcodes profile/version to core/450. In particular, TBuiltIns::initialize is specialized to remove most of what is not supported or won't be supported by ANGLE. The result of this function is parsed with TParseContext::parseShaderStrings which is a performance bottleneck. This change shaves about 300KB off of ANGLE's binary size and reduces the cost of SetupBuiltinSymbolTable to nearly a sixth. Signed-off-by: Shahbaz Youssefi <ShabbyX@gmail.com> |
||
---|---|---|
.. | ||
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 | ||
pch.cpp | ||
pch.h | ||
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.