Google Git
Sign in
dawn / tint / b27fdd1426692444d2122ea5f2bf058691fd225a
commitb27fdd1426692444d2122ea5f2bf058691fd225a[log] [tgz]
authorTint team <no-reply@google.com>Fri May 31 12:27:01 2024 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri May 31 12:27:01 2024 +0000
tree6461d1b8faa7f02cc1727e19fd7c5da23a8138ab
parent63ed5f8c80aa2bbada9b30a3dabd6bd59ee3d968 [diff]
Import Tint changes from Dawn

Changes:
  - ca3c3f474ad7a599843ea0281c92a43b12ac9af9 Update ir::builder includes. by dan sinclair <dsinclair@chromium.org>
  - 1caf8c690ce75667a38d7fce4ab2886f8fc66b98 Cleanup some includes by dan sinclair <dsinclair@chromium.org>
  - 2320e63eb964badefc9166be1c07d0a516b87e63 Add check for option to tint::glsl::writer::ASTFuzzer by Ryan Harrison <rharrison@chromium.org>
  - 9f0b65f8a6eefb2b7960522c701946c60fa07489 Remove unused inferred template default parameter. by dan sinclair <dsinclair@chromium.org>
  - 7eb5f8c515572ac254338f18feae8dc1f47c69b7 [spirv] Fix terminator creation in MergeReturn by James Price <jrprice@google.com>
  - e93ab20875ca3303ab2a1bc543debdda83c755f6 [tint][wgsl][fuzz] Add more to dictionary.txt by Ben Clayton <bclayton@google.com>
  - 1b0c89597857ca23dbdd33f2b472b222915af08e [ir] Fix store target validation highlight by James Price <jrprice@google.com>
  - 77ac3f1ee9557561e80f8df2391381496a96d01f [ir] Add RemoveTerminatorArgs transform by James Price <jrprice@google.com>
  - 1ffa4e1ee10b3c2a81d64ecb3efc46b827874d2d [tintd] Allow all extensions and features by James Price <jrprice@google.com>
GitOrigin-RevId: ca3c3f474ad7a599843ea0281c92a43b12ac9af9
Change-Id: I2b9f8c7144fe38fe5c32b1b93139ed6c648f2ca6
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/191080
Commit-Queue: James Price <jrprice@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: James Price <jrprice@google.com>
25 files changed
tree: 6461d1b8faa7f02cc1727e19fd7c5da23a8138ab
  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.