Google Git
Sign in
dawn / tint / fbfa641c298d775e6c8cec728ac9d2fa45ab493d
commitfbfa641c298d775e6c8cec728ac9d2fa45ab493d[log] [tgz]
authorTint team <no-reply@google.com>Wed May 29 12:37:10 2024 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 29 12:37:10 2024 +0000
tree6b41b710fd6105e34e6afe9b031fd3facc314e6b
parent9fe266b4261082bd9ec9e3bcc6c58d1073b9951d [diff]
Import Tint changes from Dawn

Changes:
  - 548ee54a9742b6368325414911deef9e21d986ee Add missing bits of build support for libprotobuf-mutator by Ryan Harrison <rharrison@chromium.org>
  - cc43f15ddc5e0a25cbdc141610483b2be2b941d6 Tint: Add `dual_source_blending` as a valid WGSL extension by Jiawei Shao <jiawei.shao@intel.com>
  - d7dfc6c14ee7b97e4ff6dd85fd0aa7bbe708f233 Tint: Add input attachments support to spirv AST printer. by Le Hoang Quyen <lehoangquyen@chromium.org>
  - 10d0b65f6e0d3d7b689217fbe3cc60d08e94480b Tint: Add input attachments support to spirv IR printer. by Le Hoang Quyen <lehoangquyen@chromium.org>
  - c224131e83b98f9525b511fdc79a78d478b67146 Tint: Add inputAttachmentLoad to core.def, wgsl.def, IR by Le Hoang Quyen <lehoangquyen@chromium.org>
  - 985b4e8921edd65074abc577eb80bb88639eb415 [msl] Populate Output::workgroup_allocations by James Price <jrprice@google.com>
  - 7796bc02b45e2f9f54cb6bd67c6d36d6ef125d9d [tint][ast][msl] Remove the need for SingleEntryPoint to ... by Ben Clayton <bclayton@google.com>
  - 0be0f1bda4660667da6f5f30ac79d603c359102a Fix misc-include-cleaner warnings from clang-tidy by David Neto <dneto@google.com>
  - d8bde2c4c5d124ac9997ad431aac172b1963751c [tint][ir] Validate compute entry point has workgroup_size by Ben Clayton <bclayton@google.com>
  - b4bd417d7c423b95f05de5c3b5f1887c5226a7b4 [tint][ast][msl] Skip the MSL fuzzer if the program has m... by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: 548ee54a9742b6368325414911deef9e21d986ee
Change-Id: I9031fdf1b7d60ec2baf3bee208950e9ee29a5df5
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/190640
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: James Price <jrprice@google.com>
Reviewed-by: James Price <jrprice@google.com>
75 files changed
tree: 6b41b710fd6105e34e6afe9b031fd3facc314e6b
  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.