Google Git
Sign in
dawn / tint / 1cb1050884945b12365930e74544258e080e3db5
commit1cb1050884945b12365930e74544258e080e3db5[log] [tgz]
authorTint team <no-reply@google.com>Fri Feb 02 20:35:03 2024 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Feb 02 20:35:03 2024 +0000
treeb64cbcbf5f41b9994ab97fc80ea5d0098ec24978
parentc0c0cab46a962afc2d4aeae947fef9ef3b678285 [diff]
Import Tint changes from Dawn

Changes:
  - f8865ecde66b5bc462c86e17afd8ec7c33d0e926 [tint][wgsl] Improve 'cannot take address of' diagnostic by Ben Clayton <bclayton@google.com>
  - dd852a700405828f7339a89b89ea807f96500c87 [tint] Add f16 overload of subgroupBroadcast() by James Price <jrprice@google.com>
  - 0f8c1cabc4d0b1b98a2eb173c83bef00b7e002a9 Fix workgroup_storage_size computation by Gregg Tavares <gman@chromium.org>
  - 01fa7c86fdcfbbf81de4bccf1144b1c6d2f710a6 Various fixes for Win32 CTS coverage by Ben Clayton <bclayton@google.com>
  - a0b1a226c1e1d64e947e1626f0a32b4ddb900523 [tint][utils] Replace std::unordered_map with Hashset in ... by Ben Clayton <bclayton@google.com>
  - f70336708248f8e2b77187f552c220c473e2372c [tint][core] Remove dead code by Ben Clayton <bclayton@google.com>
  - ce5c2650c889910ec154401f7079473f7d90b97a [tint][utils] Simplify pointer hashing by Ben Clayton <bclayton@google.com>
  - 7a27d6cfab9a161d8af3d0946b36970cf6694938 [tint][utils] Reimplement Hashmap / Hashset. by Ben Clayton <bclayton@google.com>
  - 3d49551542867b3d9d3c02c9dadf61ffdcc0074d [tint][core] Fix tests by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: f8865ecde66b5bc462c86e17afd8ec7c33d0e926
Change-Id: Iae6f9d13e5b3974f1bada4a4eb1e486a3af9998d
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/172820
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
107 files changed
tree: b64cbcbf5f41b9994ab97fc80ea5d0098ec24978
  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. Doxyfile
  22. LICENSE
  23. OWNERS
  24. PRESUBMIT.py
  25. README.md
  26. 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.