Import Tint changes from Dawn

  - 3b2ce130b6ea810e881bac3cc9c0ba24a6d03314 Stay within lex'd token bounds. by dan sinclair <>
  - 08659d098db1c66730bfb3185155e5ebbdf266ac tint/ast: Generate ast::TexelFormat from intrinsics.def by Ben Clayton <>
  - fe8e6ee6827ca214ac789765afc1b939f0c2228a tint/ast: Generate ast::BuiltinValue from intrinsics.def by Ben Clayton <>
  - 9a6acc419eb550a46bf77c4174c521ddfc5ad98d tint: Add tint::OverrideId by Ben Clayton <>
  - b2306e27fcc99443e5e73e0109e8bc018c1aae8b Drop line and col in intrinsic file by dan sinclair <>
  - 8dbd4d028073c22594f4457ebd6c806afd439d41 Add storage_class error reporting to generators and trans... by dan sinclair <>
  - f330229de5a135f4430756dd3d244bd1bddae6a4 tint/ast: Rename Builtin to BuiltinValue by Ben Clayton <>
  - f50d56aa05a63b614c49adaab5f3ced3b100ceb1 tint/ast: Generate ast::Extension from intrinsics.def by Ben Clayton <>
  - a1571ac40308b2551eb51201f00819ca49f7120e tint/inspector: Use a std::optional for workgroup_size by Ben Clayton <>
  - a123b892a57598308577be70286abf74f9c17c64 tint/ast: Generate ast::StorageClass from intrinsics.def by Ben Clayton <>
  - bf8ee3549875457ee5019b83923bf0205763cfab const eval of clamp by Antonio Maiorano <>
  - 4de90f0bb158271919658ec169bd9ba24ebb3d0c const eval of atan2 by Antonio Maiorano <>
GitOrigin-RevId: 3b2ce130b6ea810e881bac3cc9c0ba24a6d03314
Change-Id: I2e50cb137494bd180c00ae9f491767eba5ed5c92
Reviewed-by: Ben Clayton <>
Commit-Queue: Ben Clayton <>
Kokoro: Kokoro <>
126 files changed
tree: d853608ba38cdc30bb3fca274b389fd89fb5975a
  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.