| Age | Commit message (Collapse) | Author |
|---|
|
These represent unquoted symbols - typically referred to as identifiers.
This has been renamed as quoted strings will be added to the tokenizer in another change.
|
|
The SizeInBytes name matches what is used in the DatumType class.
|
|
The parser test file is getting large and hard to work with. It's
difficult to find what has been tested and where the tests are, along
with causing merge conflicts.
This CL splits the monolithic parser_test file into files based on
what's being parsed.
|
|
This Cl adds CLEAR_COLOR parsing into the AmberScript parser. The EXPECT
EQ was also fixed to use the correct 0-255 range instead of 0.0-1.0
range for colour expectations.
Fixes #344.
|
|
This change introduce the COPY command to amberscript,
which enables to copy a buffer content into an other
buffer.
|
|
This CL adds the EXPECT EQ command into amber script.
|
|
This CL removes the data_ pointer in the amber::Buffer object. The data
is transferred into the values_ list as early as possible.
|
|
The draw command expects the width and heigth passed into the Draw Rect
command to be the full width/height we want to draw. Not a scale of -1
to 1. This means that we would only draw one corner of the screen
instead of the entire screen.
|
|
This CL updates the probe commands to contain the buffers needed instead
of providing the pipeline.
|
|
This CL adds the EXPECT parsing for EQ_RGB and EQ_RGBA expectations.
This is enough to allow a clear.amber script to be written.
Issue #345.
|
|
Previously the buffer type existed in both the Buffer and
Pipeline::BufferInfo. These buffer types could diverge, which could
cause issues with thinking the buffer is of an incorrect type.
This CL removes the buffer type from BufferInfo and always uses the
buffer to retrieve the type.
|
|
This CL adds parsing for the CLEAR command in AmberScript.
|
|
This CL adds parsing of the RUN commands for compute and DRAW_RECT
instances to AmberScript.
|
|
This CL adds parsing for the generic buffer bindings.
|
|
[amberscript] Parse VERTEX_DATA and INDEX_DATA.
This CL adds parsing of VERTEX_DATA and INDEX_DATA binding commands
inside the PIPELINEs of amberscript.
|
|
This CL adds parsing for the AmberScript color and depth attachments. It
also updates the pipelines to create a default color or depth attachment
if one is not provided.
|
|
This CL adds a framebuffer width and height to the pipeline class and
adds parsing of the FRAMEBUFFER_SIZE command.
|
|
This CL updates the AmberScript parser to handle the changes to the
ENTRY_POINT parameter.
|
|
This CL updates the AmberScript parser to handle the changes to the
BUFFER syntax.
|
|
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.
|
|
* Count line numbers in VkScript
This CL adds line counting to the VkScript parser to give more context
in error messages.
Issue #113
|
|
This CL merges the vk and amber Script classes along with the vk and
amber Executor classes.
|
|
This CL allows for Buffers to be described by a DatumType (like the
indices buffers) or by a Format type. The VertexNodes have been removed
and converted to Format type buffers.
|
|
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.
|
|
Add cpplint
|
|
This CL adds parsing for the various buffer commands available in
AmberScript.
BUFFER vertex my_buf DATA_TYPE vec2<int32> SIZE 5 FILL 0
BUFFER index my_buf DATA_TYPE int32 SIZE 5 SERIES_FROM 2 INC_BY 1
BUFFER framebuffer my_frame DIMS 256 256
BUFFER storage my_store DATA_TYPE uint32 DATA
1 2 3 4 5
END
For each type, the internal buffer will be filled with the data before
it leaves the parser.
Fixes #5
|
|
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.
|
