Import Tint changes from Dawn

  - 04e38e884b952543601bb05c85eb175f20eb0b8c [tint][resolver] Mark all short-circuited RHS expressions... by Ben Clayton <>
  - dd89ce45f54704e4cdd147f295ba872b8af50a43 [glsl] Reorder GLSL transforms. by dan sinclair <>
  - f58479706392f005b0c5e85d0ccc688f2db8d7e1 [ir] Fix Disassembly::EmitOperandList() with count by James Price <>
  - d42ff1655946e18869808cb7b4d3930da2d9b108 [ir] Track BreakIf as a loop exit by James Price <>
  - a002503e66599d1c73760953a3952e64aff114df [ir] Validate loop body with params has initializer by James Price <>
  - a7e91f5d02c9f5acad3104f91c4ad19f68a05c6a [spirv] Do not add exit phi for loop initializer by James Price <>
  - 02cf91129de9237ec0dd58430b3fb6c2b971b5b0 [msl] Implement ShaderIO transform by James Price <>
  - c509bb3757c02beecfd6d74ef7aae9ee94b1e3ed [tint][ir][spirv] Deduplicate storage textures with diffe... by Ben Clayton <>
  - d82c5cbc6ad588606f4372647d45f062d13318c5 Tint: Add support for input_attachment_index in inspector. by Le Hoang Quyen <>
  - aefe7d2223a97b0b1580b4f77e2dff40b6c56406 OpenGLES: baseVertex, baseInstance workaround. by Stephen White <>
GitOrigin-RevId: 04e38e884b952543601bb05c85eb175f20eb0b8c
Change-Id: I465e514bcd76bfc566a8717501f3a4f44ba28547
Reviewed-by: James Price <>
Commit-Queue: James Price <>
Kokoro: Kokoro <>
38 files changed
tree: 9c884233ff2eb3b0c796cb56d166f5952bfdb149
  1. .vscode/
  2. build_overrides/
  3. docs/
  4. include/
  5. infra/
  6. kokoro/
  7. scripts/
  8. src/
  9. third_party/
  10. tools/
  11. .clang-format
  12. .gitignore
  13. .gn
  16. CMakeLists.txt
  17. CMakeSettings.json
  19. CPPLINT.cfg
  20. DEPS
  22. OWNERS
  25. standalone.gclient


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.