Google Git
Sign in
dawn / tint / 5004fa93425bb807935f15453b4b61735013dfd2
commit5004fa93425bb807935f15453b4b61735013dfd2[log] [tgz]
authorTint team <no-reply@google.com>Thu May 23 14:16:26 2024 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu May 23 14:16:26 2024 +0000
tree4e16c795b3947e8a591420e2babc8fbac3f09b75
parent26fcef8b547e5d66a374de7ce27304c088608bd2 [diff]
Import Tint changes from Dawn

Changes:
  - 6cbdd1d3013d7f24b8b349764eee47b97cf9a0b5 [ir] Track the index of a function parameter by James Price <jrprice@google.com>
  - 9af2b6ff49d992656023ece90c152f4eb1ab7cfc Tint: add InputAttachment type class & definition in wgsl... by Le Hoang Quyen <lehoangquyen@chromium.org>
  - 97b837aa6a215b112d8651da3386348e4a61ce76 Place guard for tint_executable outside of definition by Ryan Harrison <rharrison@chromium.org>
  - f9a9918278ec1142979c6b2d0e43dc3406f66eda Tint: add chromium_internal_input_attachments extension t... by Le Hoang Quyen <lehoangquyen@chromium.org>
  - 7e9f1a6fc5524980fe583bfddf9b0e130b36ad8b [tint][ir] Wrap SymbolTable and type::Manager once by Ben Clayton <bclayton@google.com>
  - 76030517393bd58e742830cd669dd8a29a92f0e3 [tint][core] Assert that Splat and Composite type matches... by Ben Clayton <bclayton@google.com>
  - e4076accc7ce8d21ccc1c50be435818ed8ddec5b [tint] Use templated types for Composite() where possible by Ben Clayton <bclayton@google.com>
  - fb7ee3d5a2d31fa862987dc30ebddae5522909be [tint][core] Splat: Infer count from type by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: 6cbdd1d3013d7f24b8b349764eee47b97cf9a0b5
Change-Id: Ie29de169976b4e9f2378057ea63f5bdee7d2ba6a
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/189660
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: David Neto <dneto@google.com>
Commit-Queue: dan sinclair <dsinclair@google.com>
50 files changed
tree: 4e16c795b3947e8a591420e2babc8fbac3f09b75
  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
  14. AUTHORS
  15. BUILD.gn
  16. CMakeLists.txt
  17. CMakeSettings.json
  18. CODE_OF_CONDUCT.md
  19. CPPLINT.cfg
  20. DEPS
  21. LICENSE
  22. OWNERS
  23. PRESUBMIT.py
  24. README.md
  25. standalone.gclient
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.