Age | Commit message (Collapse) | Author |
|
Enable shader optimizations
* During shader compilation, if SPIRV-Tools are enabled run requested
optimizations for the shader
* these optimizations are pipeline specific
* added a test
|
|
Fixes #433
* Adds COMPILE_OPTIONS command
* currently only supported for OPENCL-C shaders
* plumbed to Clspv
* Added tests
* Add docs
|
|
Fixes #426
* New BIND subcommands to specify kernel args by name or ordinal
* storage class specification is optional, but checked for consistency
* clspv compiles parse descriptor map (partially) into
Pipeline::ShaderInfo
* Bindings updated before pipeline creation
* added compiler and pipeline tests for new functionality
* added new end-to-end test
* Add documentation
* Buffer storage class specification is now optional for OpenCL-C
|
|
Specify target version for GLSL compilation
Fixes #549
|
|
The SizeInBytes name matches what is used in the DatumType class.
|
|
The CTS requires code to not use c++11. This CL converts the various
c++11-ism's in the Amber API to C++03.
|
|
This CL allows spriv-tools, googletest and shaderc to be disabled at
build time. (Disabling spriv-tools will also disable shaderc).
|
|
Break apart Amber::Execute method.
This CL splits Amber::Execute into a parse and execute step. The Parse
step accepts a Recipe to fill out, that Recipe is then passed into the
Execute step. The recipe, in the future, will allow retrieving
information about the given script.
|
|
This CL extends the Amber interface to allow a Shader map to be
provided. This map allows the caller to pre-compile the shaders and
provide the name to data mapping. The ShaderCompiler will then pull from
the map before attempting to do a compile.
|
|
Add cpplint
|
|
Amber is a multi-API shader test framework.
Amber lets you capture and communicate shader bugs with the fluidity and ease of a scripting flow:
* No graphics API programming is required.
* WIP: Supports Vulkan and [Dawn][Dawn] graphics APIs.
* A single text string (or file) maps to a single graphics API pipeline test case. The text includes:
* Input data, including buffers and images.
* Shaders.
* Expectations for the result of running the pipeline.
* Shaders can be expressed in binary form (as hex), in SPIR-V assembly, or in a higher level shader language.
* After executing the pipeline, result buffers and images can be saved to output files.
This is not an officially supported Google product.
|