Google Git
Sign in
dawn / tint / 2862d50add2f38bd79ca4f9e3cba67cc669e6d56
commit2862d50add2f38bd79ca4f9e3cba67cc669e6d56[log] [tgz]
authorTint team <no-reply@google.com>Fri May 24 13:02:37 2024 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 24 13:02:37 2024 +0000
treea29a1f973cc392b776819dc158c20f65231c0829
parent5004fa93425bb807935f15453b4b61735013dfd2 [diff]
Import Tint changes from Dawn

Changes:
  - 1b0266e46488b89b0a98ccb9c538d80cf7436c91 [tint][ir] Add Decode() overload that takes a protobuf st... by Ben Clayton <bclayton@google.com>
  - efa2c60efb27f761a0c6e265c39d84d8371ecf28 [tint][type] Move private validity checks to static membe... by Ben Clayton <bclayton@google.com>
  - f403412d25f8dd5d8f5e7c17232e53232c78ea78 [tint] Add constant::Invalid by Ben Clayton <bclayton@google.com>
  - a6788bdfee90a790c2e4991ba795e2a8a61635eb [tint][core] Test that OOB Splat::Index() returns nullptr by Ben Clayton <bclayton@google.com>
  - e4e461377ef4d02328f0f20b1ef79897f14d75b0 Tint: Add input_attachment as builtin type. by Le Hoang Quyen <lehoangquyen@chromium.org>
  - 59eb7f31f5507fbddcfead963581523c78e69b8f Tint: Add input_attachment_index attribute class and def ... by Le Hoang Quyen <lehoangquyen@chromium.org>
  - 81da61165530deb3049ad38a54309278c3565413 Make textureDimensions(texture_external) use the visible ... by Corentin Wallez <cwallez@chromium.org>
  - 4e043e9741d726a213b588a369d0c5623370c910 [msl] Add ArrayLengthFromUniform transform by James Price <jrprice@google.com>
GitOrigin-RevId: 1b0266e46488b89b0a98ccb9c538d80cf7436c91
Change-Id: Idf601440a3444bcda88f60ebc28becf157d7d013
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/189661
Commit-Queue: James Price <jrprice@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: James Price <jrprice@google.com>
54 files changed
tree: a29a1f973cc392b776819dc158c20f65231c0829
  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.