Google Git
Sign in
dawn / tint / 5aca651c524caca8ac85962d1dff378238671eba
commit5aca651c524caca8ac85962d1dff378238671eba[log] [tgz]
authorTint team <no-reply@google.com>Mon Jun 20 10:53:10 2022 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jun 20 10:53:10 2022 +0000
tree722e343751d417cad942f1b9df648fca1c9ce213
parent686f36a36ccb6f60f39b3ade9700a72631081ae6 [diff]
Import Tint changes from Dawn

Changes:
  - a05e31b5af60df895c6e88bdeddb4bac0077ec64 tint/resolver: Clean up parameter resolving by Ben Clayton <bclayton@google.com>
  - 0a4e2a1373a9b58c5e7170063fcb96d8bdbb576c Remove NOLINT lines from c++17 headers by dan sinclair <dsinclair@chromium.org>
  - c7f7ca3d9ec1bfabb4061d73848a0a9d1568b413 tint: Simplify ++/-- handling in transform by James Price <jrprice@google.com>
  - d713669329430ccebbf2c0eb1d3667388adddfcb Tint: Fix VectorizeScalarMatrixConstructors to run for re... by Zhaoming Jiang <zhaoming.jiang@intel.com>
  - 889a499ef471aa16918f701da4988d1c3b38146d Remove test/tint/BUILD.gn. by dan sinclair <dsinclair@chromium.org>
  - ecb46b33ccf0aa519ee97577bbb494fb6f5b0630 tint/resolver: Move texture validation to the right place by Ben Clayton <bclayton@google.com>
  - dcdf66ed5b286b8b67bfb633b86f298f8910f344 tint/ast: Derive off `ast::Variable` by Ben Clayton <bclayton@google.com>
  - be6fb2a8d2f3c574ef0b3ced7b19c3a6541ece35 tint: Fix emitting vector constant in HLSL writer by Zhaoming Jiang <zhaoming.jiang@intel.com>
GitOrigin-RevId: a05e31b5af60df895c6e88bdeddb4bac0077ec64
Change-Id: I5a23ae5d86ab4b6ef364995cc86a515b2359928c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/94180
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
82 files changed
tree: 722e343751d417cad942f1b9df648fca1c9ce213
  1. .vscode/
  2. build_overrides/
  3. docs/
  4. include/
  5. infra/
  6. kokoro/
  7. src/
  8. test/
  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. Doxyfile
  22. LICENSE
  23. OWNERS
  24. PRESUBMIT.py
  25. README.md
  26. standalone.gclient
  27. 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.