Google Git
Sign in
dawn / tint / 13b967fb40a0e1c5ae83c31c806e8cf81bb42815
commit13b967fb40a0e1c5ae83c31c806e8cf81bb42815[log] [tgz]
authorTint team <no-reply@google.com>Thu Jul 21 13:44:01 2022 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 21 13:44:01 2022 +0000
tree9ed909c9c90823ed696f38cd4f1a288578c3a221
parent55b93f1ce5fc77c431737a916441a6f2a4dfd86c [diff]
Import Tint changes from Dawn

Changes:
  - 3b8b9699d69f1eeb6fadddcbe56ffc68ae57715e tint: Implement const eval of unary minus by Antonio Maiorano <amaiorano@google.com>
  - eb02cd33012e1a461109b13c38335db9e711355e Regex fuzzer: replace function calls with builtins by Alastair F. Donaldson <alastair.donaldson@imperial.ac.uk>
  - ca21fa019fa6e706320661a35e78ddcc6132384c Update dictionary for fuzzing by Alastair F. Donaldson <alastair.donaldson@imperial.ac.uk>
  - 46c32d882d6d7a83e6c11e0b986a3f9d91200f1b Early out Is checks. by dan sinclair <dsinclair@chromium.org>
  - 633cdf41cc40ff97619093c0784a87cd65a2b187 tint/resolver: Make the F16 ban error message show a sing... by Corentin Wallez <cwallez@chromium.org>
  - e4df87fd017cd1d3eacbfbed57e521f6f7733936 Regex fuzzer: Add break and continue statements by Alastair F. Donaldson <alastair.donaldson@imperial.ac.uk>
  - 84f7830874fc28c173448f8291ad8c2571fda573 Regex fuzzer: replace operators by Alastair F. Donaldson <alastair.donaldson@imperial.ac.uk>
  - 056f97a9e53215398dfbd9145714e678c872a070 tint: Add a benchmark for atan2 const eval by Ben Clayton <bclayton@google.com>
  - 853cbadc8fa6c5eaa2c6d2d55a5f10b6a9ab94d4 Clean regex fuzzer API by Alastair F. Donaldson <alastair.donaldson@imperial.ac.uk>
GitOrigin-RevId: 3b8b9699d69f1eeb6fadddcbe56ffc68ae57715e
Change-Id: I6a489442f5fff4d39396cc9ced675564730d2aa7
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/96660
Commit-Queue: Ben Clayton <bclayton@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
45 files changed
tree: 9ed909c9c90823ed696f38cd4f1a288578c3a221
  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.