Google Git
Sign in
dawn / tint / fea03191403af248f7b1609e4b0c842752efcacc
commitfea03191403af248f7b1609e4b0c842752efcacc[log] [tgz]
authorTint team <no-reply@google.com>Thu Oct 19 14:51:20 2023 +0000
committerBen Clayton <bclayton@google.com>Thu Oct 19 14:51:20 2023 +0000
tree80f94b1a9244de9a82255b24fce0d8e71d1359ac
parent67a3ef8b566c3c4bfbfdd700e63d584bb77242ca [diff]
Import Tint changes from Dawn

Changes:
  - 4249124e3c5109152d5323c482f4751017ad5165 GLSL, HLSL: fix atomicSub() output. by Stephen White <senorblanco@chromium.org>
  - 45c2ba269b0f485b591b642474e53ac9f60b98f8 tint: fix TINT_PRINT_PROGRAM_FOR_EACH_TRANSFORM compilation by Antonio Maiorano <amaiorano@google.com>
  - 5d5be56d511739aa9199e4dd5d078c983630b2c8 Regenerate build files by Austin Eng <enga@chromium.org>
  - 2f8af086f8bbf03ff343edb56a95921de57dce61 [ir][glsl] Skeleton of GLSL IR backend by dan sinclair <dsinclair@chromium.org>
  - cc2516ac15ebeb6c3c07a427a76d6b57832d3154 Relicense Dawn to BSD 3-Clause by Austin Eng <enga@chromium.org>
  - eee2a8328adc18a3cef5d9db11be61899fe64f56 [tint][ir] Rename Binary::Kind to BinaryOp by Ben Clayton <bclayton@google.com>
  - a14737a1309aa74692e011c9a0b4d4071d674796 Move tint writer options into GLSL request. by dan sinclair <dsinclair@chromium.org>
GitOrigin-RevId: 4249124e3c5109152d5323c482f4751017ad5165
Change-Id: I37a1d1c7a4e48dd32ea41f674c1c552db009c271
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/156840
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
2001 files changed
tree: 80f94b1a9244de9a82255b24fce0d8e71d1359ac
  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
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.