Google Git
Sign in
dawn / tint / 2e4901757ced7452bcfd02fdacc8c71f537892c3
commit2e4901757ced7452bcfd02fdacc8c71f537892c3[log] [tgz]
authorTint team <no-reply@google.com>Tue Aug 23 13:09:30 2022 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Aug 23 13:09:30 2022 +0000
treec55caedaceaf9d6ffb8d0c7eadfb5ed5072e191f
parent5c0457c78570fe914c02b8940d43a230572bc5ac [diff]
Import Tint changes from Dawn

Changes:
  - 64b09959f7ae6c78ef8f3d7d55b5b746ffb22af9 Update `type_decl` and `primary_expression` by dan sinclair <dsinclair@chromium.org>
  - 08d735e6a91d327e1ddddb3d1b955422ad09d885 Add missing relational_expression.post.unary_expression c... by dan sinclair <dsinclair@chromium.org>
  - a838e34954c32b115ba3de177672a35193152c4d Handle peeking past placeholder elements. by dan sinclair <dsinclair@chromium.org>
  - 393de082d3a3e8c64127ab168735efe61632e601 Add `mat_prefix`, `vec_prefix`, `callable` and `type_decl... by dan sinclair <dsinclair@chromium.org>
  - 9284f8ab55f64f8e035ece0ffc54d093bddb6d2d Add test for let with complex constructor by dan sinclair <dsinclair@chromium.org>
  - 96a7d5a6bd2506112a12e2dc4e435e19631a2be0 Add some parenthesis. by dan sinclair <dsinclair@chromium.org>
  - e76521153f3f0f4341ee89323565bb978b2062dd Fixup shift_expression parsing. by dan sinclair <dsinclair@chromium.org>
  - ee25586aec81e62f22a594fc3ab2669ecfd92c2b Sync `expression` grammar element with WGSL spec. by dan sinclair <dsinclair@chromium.org>
GitOrigin-RevId: 64b09959f7ae6c78ef8f3d7d55b5b746ffb22af9
Change-Id: Ia8a35c3c61b935bf0b814090f95a92b55303f31c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/100121
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
14 files changed
tree: c55caedaceaf9d6ffb8d0c7eadfb5ed5072e191f
  1. .vscode/
  2. build_overrides/
  3. docs/
  4. include/
  5. infra/
  6. kokoro/
  7. src/
  8. third_party/
  9. tools/
  10. .clang-format
  11. .gitignore
  12. .gn
  13. AUTHORS
  14. BUILD.gn
  15. CMakeLists.txt
  16. CMakeSettings.json
  17. CODE_OF_CONDUCT.md
  18. CPPLINT.cfg
  19. DEPS
  20. Doxyfile
  21. LICENSE
  22. OWNERS
  23. PRESUBMIT.py
  24. README.md
  25. standalone.gclient
  26. 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.