Import Tint changes from Dawn

Changes:
  - 517278ac08a8b275d20352fd0cf131ea7ddc06ef Move text/unicode into utils. by dan sinclair <dsinclair@chromium.org>
  - 12fa30389926a804e6f25414ea987817e2c364e0 Move castable into utils. by dan sinclair <dsinclair@chromium.org>
  - e6e5998e2b4c0178fa73e29acd697b21bcabdfc5 Cleanup GLSL writer. by dan sinclair <dsinclair@chromium.org>
  - c480632ed60e27a782be9077bba56d5d2f006e9c Setup ArrayLength transform for MSL benchmark by dan sinclair <dsinclair@chromium.org>
  - e16ed7ccc28acce334947ad3e9dba589b7724874 Make more SymbolTable methods string_view. by dan sinclair <dsinclair@chromium.org>
  - 055900549456dc9e88486011108a8fc23383d75b Move traits into utils. by dan sinclair <dsinclair@chromium.org>
  - d21e2d64ec279e614038c2ecd835289b6e0079b8 Convert VariableUser vector over to utils::Vector. by dan sinclair <dsinclair@chromium.org>
  - 8fc9b862143991d28ad930e5dd00a3c28a92a018 CMake: Add TINT_EXTERNAL_BENCHMARK_CORPUS_DIR by Ben Clayton <bclayton@google.com>
  - 5f4847c23ea63ec4a606008a7832f8669b1899d2 tint/sem: Make BindingPoint optional by Ben Clayton <bclayton@google.com>
GitOrigin-RevId: 517278ac08a8b275d20352fd0cf131ea7ddc06ef
Change-Id: I9d9436cee5bc5f69a99af9d88990c24d63f86a13
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/128200
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
324 files changed
tree: c546ee9605c0d1116f8e186a37ffbde4d8c599f0
  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
  27. tint_overrides_with_defaults.gni
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.