Google Git
Sign in
dawn / tint / 942ac0b0ae228fd16b56a487526217365068b2bb
commit942ac0b0ae228fd16b56a487526217365068b2bb[log] [tgz]
authorTint team <no-reply@google.com>Mon Apr 24 11:16:02 2023 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 24 11:16:02 2023 +0000
tree9258255b7dd8fb6ebd33cfd0044cc9de9b421bd8
parent58ad0b46cc4cc13f36d7f9908070120ade931db1 [diff]
Import Tint changes from Dawn

Changes:
  - 9b726858ff7bf6136c027c4a6074ce64175f3c71 Fast path ASCII in unicode decode. by dan sinclair <dsinclair@chromium.org>
  - ca1b90445654566db21155b8866834bddfbb2382 IWYU: add stdint.h for int types in tint::utils by Stephan Hartmann <stha09@googlemail.com>
  - de42feb949c2d82de37079514a26416544fc5dd0 tint: Add vec2(), vec3(), vec4() by Ben Clayton <bclayton@google.com>
  - 5a5b7dfe92b0e3a72c6a625d670c30b4a754bd1b Add builtin information to Symbol. by dan sinclair <dsinclair@chromium.org>
  - d1d1bf7135d4cd9092a1cf601071a53334c0b21d Split base_src apart. by dan sinclair <dsinclair@chromium.org>
  - 7883a0cb8d2cc0922120ffcc087d629da9e55a66 tint: Add two-token form for diagnostics rule names. by Ben Clayton <bclayton@google.com>
  - 7eb37948abc28ae9ffe7539b23804d8e3c6470f8 tint/reader/wgsl: Have expect_identifier return an ast::I... by Ben Clayton <bclayton@google.com>
  - 45ff7a8c4ae718a9ffb980c174626f2683522854 Remove extra work from `is_reserved` by dan sinclair <dsinclair@chromium.org>
GitOrigin-RevId: 9b726858ff7bf6136c027c4a6074ce64175f3c71
Change-Id: Iaa572434b39a1af9f8e6f00059d6ec993ada664c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/128500
Commit-Queue: Ben Clayton <bclayton@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: Copybara Prod <copybara-worker-blackhole@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
62 files changed
tree: 9258255b7dd8fb6ebd33cfd0044cc9de9b421bd8
  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.