Import Tint changes from Dawn

Changes:
  - c970e806dbe9fe921cad7716199e1e6fa2b9be6e [ir] Emit `var` and `let` into the IR by dan sinclair <dsinclair@chromium.org>
  - 642a4f1d8c94e684c21a7fc47b75cfeee8ff656d [ir] Make dump output more consistent. by dan sinclair <dsinclair@chromium.org>
  - f26b1269bdc7a450c02aa7d198028d2501fe3678 [ir] Move `ir::Bitcast` to inherit `ir::Call`. by dan sinclair <dsinclair@chromium.org>
  - 4a2e0ad36b0ed0738a1c32fd1ddf5268231e749b [ir] Make `ir::Discard` a child of `ir::Call`. by dan sinclair <dsinclair@chromium.org>
  - bc6720b9f6554c4ee4800adeb818cc007729103c tint/type: Remove Source from Struct & StructMember by Ben Clayton <bclayton@google.com>
  - bc9e422728eb3c8d4d5b27d8394262066ba40cd4 tint: Use type::Struct where possible by Ben Clayton <bclayton@google.com>
  - 576ba1c4939288fdc1ae723f173d155a63c7c8e7 tint: Add StructMember attributes to sem. by Ben Clayton <bclayton@google.com>
  - 333cea405c5e41a7ee2cca852eee914fd724113a tint/resolver: Clean up attribute resolving by Ben Clayton <bclayton@google.com>
  - fe8a76cbbc447db0ebbe7da4818accca70900b13 [ir] Use the const eval results for expressions. by dan sinclair <dsinclair@chromium.org>
  - f00679fd72baa267cb780e2065a988b2115890bc [ir] Make ir::Instruction a ir::Value. by dan sinclair <dsinclair@chromium.org>
  - 5e344a338fcfe0737ad3933953a6dbc7164cd15c [ir] Split AST and SEM sources out of core ir. by dan sinclair <dsinclair@chromium.org>
  - 9d3af6521bf1be1bda98477d7db5c124883e1dab tint/ir: Add GN option for building the IR by James Price <jrprice@google.com>
  - 47dd30117d7d1bc425a189409f0d85ab804a36a2 tint/resolver: Resolve builtin structs by Ben Clayton <bclayton@google.com>
  - d3b09b90e31e468746d5ec643a6a6c30e4554123 tint/resolver: Add builtin_structs.h / .cc by Ben Clayton <bclayton@google.com>
  - 72d1ea4ac2b5640d9490cca6243be48da171a2bf tint/resolver: Remove duplicate nullptr check by James Price <jrprice@google.com>
  - 135ab2b39f178a2ecefd2911e82fc79eb385a43b [ir] Rename instr. by dan sinclair <dsinclair@chromium.org>
GitOrigin-RevId: c970e806dbe9fe921cad7716199e1e6fa2b9be6e
Change-Id: Ifa429a18a4655d1fe7ddae825bbcb2b0bbbf04f1
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/129760
Kokoro: Kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Commit-Queue: Ben Clayton <bclayton@google.com>
139 files changed
tree: 90e893375e01f78d63032add06bb617660fd389b
  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.