Dawn relies on a lot of code generation to produce boilerplate code, especially webgpu.h-related code. They start by reading some JSON files (and sometimes XML too), process the data into an in-memory representation that's then used by some Jinja2 templates to generate the code. This is similar to the model/view separation in Web development.
Generators are based on generator_lib.py which provides facilities for integrating in build systems and using Jinja2. Templates can be found in
generator/templates and the generated files are in
out/<Debug/Release/foo>/gen/src when building Dawn in standalone. Generated files can also be found in Chromium's code search.
Most of the code generation is done from
dawn.json which is a JSON description of the WebGPU API with extra annotation used by some of the generators. The code for all the “Dawn JSON” generators is in
dawn_json_generator.py (with templates in the regular template dir).
At this time it is used to generate:
webgpu_cpp.cpp/hC++ wrapper over the C header
webgpu.hby calling in a static or
dawn.json is a dictionary from the “canonical name” of things to their definition. The “canonical name” is a space-separated (mostly) lower-case version of the name that's parsed into a
Name Python object. Then that name can be turned into various casings with
.SNAKE_CASE(), etc. When
dawn.json things reference each other, it is always via these “canonical names”.
The basic schema is that every entry is a thing with a
"category" key what determines the sub-schema to apply to that thing. Categories and their sub-shema are defined below. Several parts of the schema use the concept of “record” which is a list of “record members” which are a combination of a type, a name and other metadata. For example the list of arguments of a function is a record. The list of structure members is a record. This combined concept is useful for the dawn_wire generator to generate code for structure and function calls in a very similar way.
A record is a list of record members, each of which is a dictionary with the following schema:
"type"a string, the name of the base type for this member
"annotation"a string, default to “value”. Define the C annotation to apply to the base type. Allowed annotations are
"length"(default to 1 if not set), a string. Defines length of the array pointed to for pointer arguments. If not set the length is implicitly 1 (so not an array), but otherwise it can be set to the name of another member in the same record that will contain the length of the array (this is heavily used in the
foospattern in the API). As a special case
"strlen"can be used for
const char*record members to denote that the length should be determined with
"optional"(default to false) a boolean that says whether this member is optional. Member records can be optional if they are pointers (otherwise dawn_wire will always try to dereference them), objects (otherwise dawn_wire will always try to encode their ID and crash), or if they have a
"default"key. Optional pointers and objects will always default to
"default"(optional) a number or string. If set the record member will use that value as default value. Depending on the member's category it can be a number, a string containing a number, or the name of an enum/bitmask value.
"native", doesn't have any other key. This is used to define native types that can be referenced by name in other things.
"typedef" (usually only used for gradual deprecations):
"name": the name of the things this is a typedef for.
uint32_t-based enum value.
"values"an array of enum values. Each value is a dictionary containing:
"value"a number that can be decimal or hexadecimal
"valid"(defaults to true) a boolean that controls whether the dawn_native validation utilities will consider this enum value valid.
uint32_t-based bitmask. It is similar to
"enum" but can be output differently.
"callback" defines a function pointer type that can be used by other things (usually callbacks passed to method calls)
"args"a record, so an array of record members
"members"a record, so an array of record members
"extensible"(defaults to false) a boolean defining if this is an “extensible” WebGPU structure (i.e. has
nextInChain). “descriptor” structures should usually have this set to true.
"chained"(defaults to false) a boolean defining if this is a structure that can be “chained” in a WebGPU structure (i.e. has
**methods**an array of methods for this object. Note that “release” and “reference” don't need to be specified. Each method is a dictionary containing:
"return_type"(default to no return type) a string that's the name of the return type.
"arguments"a record, so an array of record members
The generator for the pieces of dawn_wire need additional data which is found in
dawn_wire_json. Examples of pieces that are generated are:
WireCmd.cpp/.hthe most important piece: the meat of the serialization / deserialization code for WebGPU structures and commands
ServerHandlers/Doers.cppthat does the complete handling of all regular WebGPU methods in the server
ApiProcs.cppthat implements the complete handling of all regular WebGPU methods in the client
Most of the WebGPU methods can be handled automatically by the wire client/server but some of them need custom handling (for example because they handle callbacks or need client-side state tracking).
dawn_wire.json defines which methods need special handling, and extra wire commands that can be used by that special handling (and will get
The schema of
dawn_wire.json is a dictionary with the following keys:
"commands"an array of records defining extra client->server commands that can be used in special-cased code path.
"skip_serialize"key that's a boolean that default to false and makes
WireCmdskip it on its on-wire format.
"commands"but in revers, an array of records defining extra server->client commands
"special items"a dictionary containing various lists of methods or object that require special handling in places in the dawn_wire autogenerated files
"client_side_structures": a list of structure that we shouldn't generate serialization/deserialization code for because they are client-side only
"client_handwritten_commands": a list of methods that are written manually and won't be automatically generated in the client
"client_side_commands": a list of methods that won't be automatically generated in the server. Gets added to
"client_special_objects": a list of objects that need special manual state-tracking in the client and won't be autogenerated
"server_custom_pre_handler_commands": a list of methods that will run custom “pre-handlers” before calling the autogenerated handlers in the server
"server_handwrittten_commands": a list of methods that are written manually and won't be automatically generated in the server.
server_reverse_object_lookup_objects: a list of objects for which the server will maintain an object -> ID mapping.