Google Git
Sign in
dawn / tint / d38b7765c882e4362c5510946315a200336f1bf2
commitd38b7765c882e4362c5510946315a200336f1bf2[log] [tgz]
authorTint team <no-reply@google.com>Wed Apr 13 19:19:51 2022 +0000
committerTint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 13 19:19:51 2022 +0000
treefa004b6226e5481f59e5c6e6112cb0e6a0c88f68
parentd2323c520c155e47d6e1103828483c8215114979 [diff]
Import Tint changes from Dawn

Changes:
  - 2517d99f351f307f0f339dc2c4173ed2e265f17d Fixup kokoro lint issue by dan sinclair <dsinclair@chromium.org>
  - 4d5723b5e57070448cbc1c832e3bcec0fa741972 Remove fuzzer CPPLINT file. by dan sinclair <dsinclair@chromium.org>
  - a5f5f5a1aafa781d40fd00ad31f608738e8d68b7 use stamp file for tint_generate_wgsl_corpus by Fumitoshi Ukai <ukai@google.com>
  - c85f8d828e717076d750327797f51cd8c5f456ec tint: Fix doxygen failure by Ben Clayton <bclayton@google.com>
  - f625a6d57e462946f2c38a4a4c611ee1939f4b53 tint: Make GLSL backend consistent with the others by Antonio Maiorano <amaiorano@google.com>
  - b5c46c30ec440899910fdabcafa3b01027bb5e9e tint: spirv writer: add a GeneralImpl to be consistent wi... by Antonio Maiorano <amaiorano@google.com>
GitOrigin-RevId: 2517d99f351f307f0f339dc2c4173ed2e265f17d
Change-Id: I2abe6ee2d1a03d4e28275187dac5c0f88ee0323c
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/86641
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
24 files changed
tree: fa004b6226e5481f59e5c6e6112cb0e6a0c88f68
  1. .vscode/
  2. build_overrides/
  3. docs/
  4. include/
  5. infra/
  6. kokoro/
  7. src/
  8. test/
  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.