Google Git
Sign in
dawn / tint / c362529e39739d3bb2cea1073839592742953e2e
commitc362529e39739d3bb2cea1073839592742953e2e[log] [tgz]
authorTint team <no-reply@google.com>Wed Jul 27 09:39:42 2022 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 27 09:39:42 2022 +0000
treeb26b930360eec7f6cbb4c99b29b8a78ac67fef20
parentb2bff596bce9513949bd9dd4b1b1b31fdd52afcc [diff]
Import Tint changes from Dawn

Changes:
  - 48085845bddacd3bd7d7146f27646d95a7b6a707 tint/ast: Clean up StorageClass enum by Ben Clayton <bclayton@google.com>
  - c768e640f429fe19740f5e8d3c7b135dd4dba685 tint/intrinsics.def: Change language for enums by Ben Clayton <bclayton@google.com>
  - 02e9ce19ecbcf422760fd12b00cefba3cf721945 tint: Make tint::ast::HasAttribute() accept multiple temp... by Ben Clayton <bclayton@google.com>
  - cde5009be385c506822749eb4f450cb551476678 tools: Shuffle 'intrinsic-gen' tooling by Ben Clayton <bclayton@google.com>
  - 62c58a076c1a33cae265f77fe54f974bff12f630 Stay at the EOF or Error token. by dan sinclair <dsinclair@chromium.org>
  - 0fba14e3c6d4bea904c3291de951578dd4a7d2db tint/val: Make DXC validation output stable by Ben Clayton <bclayton@google.com>
  - e9585f554879effaff9c80dc55bdecfe14b033b9 tint/val: Fix HLSL validation with DXC by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: 48085845bddacd3bd7d7146f27646d95a7b6a707
Change-Id: I885c9ac05232f9551aefc230c4334c66f12c284c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/97320
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
40 files changed
tree: b26b930360eec7f6cbb4c99b29b8a78ac67fef20
  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.