Google Git
Sign in
dawn / tint / 700ea45b4e6ff824e5de7ea34f5e4af694a513e9
commit700ea45b4e6ff824e5de7ea34f5e4af694a513e9[log] [tgz]
authorTint team <no-reply@google.com>Tue Mar 07 11:03:17 2023 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Mar 07 11:03:17 2023 +0000
treeb8443ba499b9b1baf113b98a7cb4bc2a3be505ac
parentfdb8787e9c1b79770bd98a8faf37fbe48a3077a4 [diff]
Import Tint changes from Dawn

Changes:
  - 142bddf7dabe2cbbbb2adfaaf0a9708aad0ba1a8 Fix #ifdefs for spvtools by Austin Eng <enga@chromium.org>
  - f244bffdd51d8c4aeddd4181025559a41de4154f Fix build of tint_cmd_helper by Austin Eng <enga@chromium.org>
  - 8525ff29da6b005381abe94023a303edc0f39c44 tint/transform/robustness: Implement predicated mode by Ben Clayton <bclayton@google.com>
  - 5e5655155110e121763e3dca13d20c3eda09167e Revert "Add writer to emit the AST." by Dan Sinclair <dsinclair@chromium.org>
  - 5ab2928f6ab2c2c9d899bf1220d4be7740f09664 Convert `strtoll` to use `std::from_chars`. by dan sinclair <dsinclair@chromium.org>
  - a753ad47a48fc0fba6e617b7ffcddc0e1fdc4b2e Add writer to emit the AST. by dan sinclair <dsinclair@chromium.org>
  - 63d0fabeb1fc11e4829256804bf776a23e8f2849 tint: Fix HLSL emission for out-of-order storage / unifor... by Ben Clayton <bclayton@google.com>
  - fd387a37c3b936a547288347bf854405ca2ec647 tint: Fix WGSL emission of const_assert by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: 142bddf7dabe2cbbbb2adfaaf0a9708aad0ba1a8
Change-Id: Ic0f52f73c9a9fa70f04d272f616db8e5abd82136
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/122880
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
37 files changed
tree: b8443ba499b9b1baf113b98a7cb4bc2a3be505ac
  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.