Import Tint changes from Dawn

Changes:
  - 5e8ee8581d802b08c189858eadbad6de8a3090fc [ir] Handle some unexpected ast nodes. by dan sinclair <dsinclair@chromium.org>
  - 97b98619e818b2cd8896ca4b2b15e3cb902bdcd4 [ir] Convert tests to use disassembler. by dan sinclair <dsinclair@chromium.org>
  - e3992f240821992499bb5ce7ffe9e5fdcee7392f [ir] Cleanup disassembler output by dan sinclair <dsinclair@chromium.org>
  - a7644371384f47db8b2486087260523cec3a4c82 [ir] Allow branching arguments. by dan sinclair <dsinclair@chromium.org>
  - 1d04cf841c5d628fe0fc19e5626fbf95b519bf55 Enable the 1D -> 2D texture transform in GLSL writer. by Stephen White <senorblanco@chromium.org>
  - fb8a6dbb5d15d208d03f25af94cf41892c27ed22 Implement a Texture1D -> Texture2D transform. by Stephen White <senorblanco@chromium.org>
  - 4a62d91a9e45ef7ca376c9ac9c9eb67a28ef55b2 [ir] Remove program in ir tests. by dan sinclair <dsinclair@chromium.org>
  - 8bcb4e9e77db4f69a2b55926e58f64c39415f3d0 [ir] Remove ast pointers. by dan sinclair <dsinclair@chromium.org>
  - 0258f276b50d708bcc4bf3ce7550252b9c6bb1aa Convert CaseSelector to IR. by dan sinclair <dsinclair@chromium.org>
  - 19bc66a3754ab5b3e2b6dd0627edad0d14601329 [ir] Cleanup some comments and un-needed code. by dan sinclair <dsinclair@chromium.org>
GitOrigin-RevId: 5e8ee8581d802b08c189858eadbad6de8a3090fc
Change-Id: I2c0de371e95d1d19f660c13d8fe2c4d0fd8bda8e
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/116372
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
33 files changed
tree: 565752209950f39028f4df214003642946786cfa
  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
  13. AUTHORS
  14. BUILD.gn
  15. CMakeLists.txt
  16. CMakeSettings.json
  17. CODE_OF_CONDUCT.md
  18. CPPLINT.cfg
  19. DEPS
  20. Doxyfile
  21. LICENSE
  22. OWNERS
  23. PRESUBMIT.py
  24. README.md
  25. standalone.gclient
  26. tint_overrides_with_defaults.gni
README.md

Tint


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.

Requirements

  • 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)

Building

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 https://dawn.googlesource.com/tint 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/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/11.0.0/lib/darwin/libclang_rt.fuzzer_osx.a

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

Issues

Please file any issues or feature requests at https://bugs.chromium.org/p/tint/issues/entry

Contributing

Please see the contributing guide in the Dawn repo.