Google Git
Sign in
dawn / tint / 25e696eb2cd448f3e8488878d9e794f83bbf6367
commit25e696eb2cd448f3e8488878d9e794f83bbf6367[log] [tgz]
authorTint team <no-reply@google.com>Fri Nov 10 11:22:41 2023 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Nov 10 11:22:41 2023 +0000
tree2d0e262f26dda45fede344cac34f1de3028c39f2
parent8027aefcb42ffc5262c4db41e8deb14f8b01221e [diff]
Import Tint changes from Dawn

Changes:
  - e50f779c2dd2cebf696366812dcaf984208a53fd [tint][resolver] Fix dual source blending validation by Ben Clayton <bclayton@google.com>
  - e30eacb0b6e8725e79c283908b7cb0c7f219ac44 [tint][resolver] Tweak diagnostic messages by Ben Clayton <bclayton@google.com>
  - 65e3824a1fc0401a10b3c8a26a461d0613bfdffc [tint][sem] Move variable attributes to separate structs by Ben Clayton <bclayton@google.com>
  - 3e56a384d541a9340164373c5640585401933b14 [tint] Add chromium_experimental_framebuffer_fetch by Ben Clayton <bclayton@google.com>
  - 9cd1619dd2d3f4290127cad201795e9325f257dc [tint] Comment the fields of core::type::StructMemberAttr... by Ben Clayton <bclayton@google.com>
  - de3f95a16bca110f452acdc80296dc9a27ab84cb [tint][resolver] Fix @index validation, tweak diagnostics by Ben Clayton <bclayton@google.com>
  - 3f8fb00ff16b80d8b7881d586cd3729640f67b1e [tint][resolver] Standardise attribute diagnostics by Ben Clayton <bclayton@google.com>
  - 0e29fcb8d4fb5820e1aab9cae8dfb48747c92570 [tint][resolver] Clean up attribute validation tests by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: e50f779c2dd2cebf696366812dcaf984208a53fd
Change-Id: I35111336b878abc204403fbc0a592c19d6a7e7a1
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/160240
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
45 files changed
tree: 2d0e262f26dda45fede344cac34f1de3028c39f2
  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.