| commit | 7e374b89cb63e5d18b6d02c06471e0ebb37f1a05 | [log] [tgz] |
|---|---|---|
| author | Tint team <no-reply@google.com> | Wed Sep 21 10:24:25 2022 +0000 |
| committer | Tint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 21 10:24:25 2022 +0000 |
| tree | 55e6d5a40e6fd4d85e96ff5edcf5e4b0ccbe2e23 | |
| parent | 8f836b2e22c1123f92e59a53da1146966dab0d3b [diff] |
Import Tint changes from Dawn Changes: - 30f51b94da225f8cbffb18ee8a9f176f6df469d0 Delete the remove_stale_autogen_files mechanism. by Corentin Wallez <cwallez@chromium.org> - 7d9140feb9a7273801400c0e7166f8d994db8ce1 spirv-reader: Refactor tracking of locally-defined values by David Neto <dneto@google.com> - e68d4506c03f1455e124271d89a9d84e5ec8ec0f tint/resolver: Consistently use utils::Result in ConstEval by Ben Clayton <bclayton@google.com> GitOrigin-RevId: 30f51b94da225f8cbffb18ee8a9f176f6df469d0 Change-Id: I7eff5c8c3034ebd5f6ede46dcca2cf073d184873 Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/103160 Reviewed-by: Ben Clayton <bclayton@google.com> Commit-Queue: Ben Clayton <bclayton@google.com> Kokoro: Kokoro <noreply+kokoro@google.com>
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.
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)Tint uses Chromium dependency management so you need to install depot_tools and add it to your PATH.
# 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
mkdir -p out/Debug cd out/Debug cmake -GNinja ../.. ninja # or autoninja
mkdir -p out/Debug cd out/Debug cmake ../.. make # -j N for N-way parallel build
mkdir -p out/Debug gn gen out/Debug autoninja -C out/Debug
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.
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
Please file any issues or feature requests at https://bugs.chromium.org/p/tint/issues/entry
Please see the contributing guide in the Dawn repo.