Import Tint changes from Dawn

  - 0ea0d4b16eaadac57d35da6e708dbc360e94289d tint/resolver: Test f16 types in materialize unittests by Zhaoming Jiang <>
  - 6835c8df3e016f4607659bfeaae840483fb1cb24 tint/reader: Parse arrays with no type / size by Ben Clayton <>
  - 86329e286b23a23d284d213e904869fbfc8a53c1 tint/cmd: Dump disassembly with --verbose by Ben Clayton <>
  - 92f2cb79b5dc13590353df83da24e023dbadb1f8 tools/gen: clang-format generated .cc, .h and .inl files by Ben Clayton <>
  - 4aa360db5d36720ae2139ea1e1c84df0a60862b5 tint/resolver: Fix null-deref. by Ben Clayton <>
  - db5d2ea4f287e8cdc22e719f2182245de1c8c375 tint/writer/wgsl: Emit inferred-type arrays by Ben Clayton <>
  - 4a6562071605a1a73c14e1b705a8e4f002d03c39 tint/resolver: Handle array() constructors by Ben Clayton <>
  - 70a43fa5b9ff0ef1f8d31e62f670e0fc86f8b33e tint: Fix doxygen error. by Antonio Maiorano <>
  - 239a92d2d00113098cee074a0548a5461c97737d tint: transform::RemovePhonies: skip builtins with no sid... by Antonio Maiorano <>
  - 6315a27778728578708d109e5f28c1e0be48aeb8 tint/resolver: Tidy up by Ben Clayton <>
  - bf32bd4e961bf82a9246d0e74b863e66073279fe tint/ast: Tighten AST definition of runtime-sized array by Ben Clayton <>
  - 8c9cc860763f871604ffb77209a167e6f9fe4bea tint/resolver: Simplify / optimize Validator::Call() by Ben Clayton <>
  - 9c4d0c941038f14c400f99a4952ae0d84ed73817 tint/resolver: Split up the Array resolving logic by Ben Clayton <>
GitOrigin-RevId: 0ea0d4b16eaadac57d35da6e708dbc360e94289d
Change-Id: I02c1053b0f39500b16b4559611eea9ffb2551188
Kokoro: Kokoro <>
Commit-Queue: Ben Clayton <>
Reviewed-by: Ben Clayton <>
29 files changed
tree: 49c1cac71e552dd7b9eca6fff2438509f05e4623
  1. .vscode/
  2. build_overrides/
  3. docs/
  4. include/
  5. infra/
  6. kokoro/
  7. src/
  8. third_party/
  9. tools/
  10. .clang-format
  11. .gitignore
  12. .gn
  15. CMakeLists.txt
  16. CMakeSettings.json
  18. CPPLINT.cfg
  19. DEPS
  20. Doxyfile
  22. OWNERS
  25. standalone.gclient
  26. tint_overrides_with_defaults.gni


Note: This repo is read-only, minimized mirror of the Dawn repo.

Tint changes should be made in the Dawn repo.

Tint is a compiler for the WebGPU Shader Language (WGSL).

This is not an officially supported Google product.


  • Git
  • CMake (3.10.2 or later)
  • Ninja (or other build tool)
  • Python, for fetching dependencies
  • depot_tools in your path

Build options

  • TINT_BUILD_SPV_READER : enable the SPIR-V input reader (off by default)
  • TINT_BUILD_WGSL_READER : enable the WGSL input reader (on by default)
  • TINT_BUILD_SPV_WRITER : enable the SPIR-V output writer (on by default)
  • TINT_BUILD_WGSL_WRITER : enable the WGSL output writer (on by default)
  • TINT_BUILD_FUZZERS : enable building fuzzzers (off by default)


Tint uses Chromium dependency management so you need to install depot_tools and add it to your PATH.

Getting source & dependencies

# Clone the repo as "tint"
git clone tint
cd tint

# Bootstrap the gclient configuration
cp standalone.gclient .gclient

# Fetch external dependencies and toolchains with gclient
gclient sync

Compiling using CMake + Ninja

mkdir -p out/Debug
cd out/Debug
cmake -GNinja ../..
ninja # or autoninja

Compiling using CMake + make

mkdir -p out/Debug
cd out/Debug
cmake ../..
make # -j N for N-way parallel build

Compiling using gn + ninja

mkdir -p out/Debug
gn gen out/Debug
autoninja -C out/Debug

Fuzzers on MacOS

If you are attempting fuzz, using TINT_BUILD_FUZZERS=ON, the version of llvm in the XCode SDK does not have the needed libfuzzer functionality included.

The build error that you will see from using the XCode SDK will look something like this:

ld: file not found:/Applications/

The solution to this problem is to use a full version llvm, like what you would get via homebrew, brew install llvm, and use something like CC=<path to full clang> cmake .. to setup a build using that toolchain.

Checking [chromium-style] issues in CMake builds

The gn based work flow uses the Chromium toolchain for building in anticipation of integration of Tint into Chromium based projects. This toolchain has additional plugins for checking for style issues, which are marked with [chromium-style] in log messages. This means that this toolchain is more strict then the default clang toolchain.

In the future we will have a CQ that will build this work flow and flag issues automatically. Until that is in place, to avoid causing breakages you can run the [chromium-style] checks using the CMake based work flows. This requires setting CC to the version of clang checked out by gclient sync and setting the TINT_CHECK_CHROMIUM_STYLE to ON.

mkdir -p out/style
cd out/style
cmake ../..
CC=../../third_party/llvm-build/Release+Asserts/bin/clang cmake -DTINT_CHECK_CHROMIUM_STYLE=ON ../../ # add -GNinja for ninja builds


Please file any issues or feature requests at


Please see the contributing guide in the Dawn repo.