Google Git
Sign in
dawn / tint / ecb38dfd9a6208f1df6f03c233cf331cc8991ac3
commitecb38dfd9a6208f1df6f03c233cf331cc8991ac3[log] [tgz]
authorTint team <no-reply@google.com>Thu Feb 08 19:37:57 2024 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Feb 08 19:37:57 2024 +0000
tree89e19678539da66d6d8c090920a668c84fe1f984
parent7f4564532eeab4141baf0d2817002e5d127da4b5 [diff]
Import Tint changes from Dawn

Changes:
  - 328ffe7fbbc04ae41312347d1a9ab6d7a8bfe2dc Revert "Add deprecated proxy methods." by dan sinclair <dsinclair@chromium.org>
  - e25ac2f0fc3a36b1210dfc5788ef61948fb3d749 [tint][utils] Add AlignedStorage by Ben Clayton <bclayton@google.com>
  - 95cada18965836843ef1ee92cffeed6623adb2d5 [tint][exe] Add --use-storage-input-output-16 flag by James Price <jrprice@google.com>
  - 2f85bc743dda22b69f280b2dd5c034f3cde4919d [spirv-writer][ast] Polyfill f16 shader IO by James Price <jrprice@google.com>
  - 7c14dbaaf61a7cf95f852c07570dcd275385b6ff [spirv-writer][ast] Only use StorageInputOutput16 if needed by James Price <jrprice@google.com>
  - e90702ebf9fe7a9edf2c1e5e824ede95ae729e03 [spirv-writer] Polyfill f16 shader IO by James Price <jrprice@google.com>
  - 2c1743ab159399f0f0154088805a3db841836926 [spirv-writer] Only use StorageInputOutput16 if needed by James Price <jrprice@google.com>
  - 9ae3ff6eee865192b7ce95da7a46474a638c0855 GLSL: run OFI if any stage uses firstInstance. by Stephen White <senorblanco@chromium.org>
  - ca9f38634fcf3f782eb59db1894046aa117e857a GLSL: set integers to precision highp. by Stephen White <senorblanco@chromium.org>
GitOrigin-RevId: 328ffe7fbbc04ae41312347d1a9ab6d7a8bfe2dc
Change-Id: Ie94905aba99133a90ef23b32579b7007c5e8fae5
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/174060
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
Commit-Queue: Copybara Prod <copybara-worker@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
31 files changed
tree: 89e19678539da66d6d8c090920a668c84fe1f984
  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.