Google Git
Sign in
dawn / tint / a464772dca9331aa4250e2c200c06e4423d3e272
commita464772dca9331aa4250e2c200c06e4423d3e272[log] [tgz]
authorTint team <no-reply@google.com>Wed Dec 07 13:25:31 2022 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Dec 07 13:25:31 2022 +0000
tree4f9624a50a1fe8e9ad309d55b4bbbc970c3c8a7e
parent6146938665bd767acf20ea72eb687b6b7ac4d1cf [diff]
Import Tint changes from Dawn

Changes:
  - 6198bea2ac17ff1a085354205e11c16d2894a2bd Dawn&Tint: Implement F16 pipeline IO by Zhaoming Jiang <zhaoming.jiang@intel.com>
  - 94751e1a7d2e9f7746bf1566ab5f339abe4d491f tint/utils: Vector::Clear: disable "maybe initialized" wa... by Jason Erb <jason.erb@sparist.com>
  - ad9cd0a141b427e0af0d7ebe89e4744dbce1a515 Add base class for sem Struct and StructMember by dan sinclair <dsinclair@chromium.org>
  - c07de73b0b56efcabc355c2a4df9211dcf1b0f30 tint/transform: Strip unused atomic builtins by Ben Clayton <bclayton@google.com>
  - 49334b05cf77d272b1eb479ad8afb1e111633365 tint/utils: Remove non-const accessors on VectorRef by Ben Clayton <bclayton@google.com>
  - 6016d1e5cdc913d405076b411584e1b56caef3f4 tint: Fix unused-but-set-parameter warning by Jason Erb <jason.erb@sparist.com>
  - 8753796aaca097153af3ccebdd0f17d80d25bb9f tint: Add PreservePadding transform by James Price <jrprice@google.com>
  - a31d89d6a330565858c1d61421015ceb7bdc3afb tint/utils: Add support for unsafe pointer downcasts by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: 6198bea2ac17ff1a085354205e11c16d2894a2bd
Change-Id: Id93347fd22429517fa2c40b9eb98fb90468a039c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/113220
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
56 files changed
tree: 4f9624a50a1fe8e9ad309d55b4bbbc970c3c8a7e
  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.