|author||Tint team <firstname.lastname@example.org>||Thu Mar 16 11:15:26 2023 +0000|
|committer||Tint LUCI CQ <email@example.com>||Thu Mar 16 11:15:26 2023 +0000|
Import Tint changes from Dawn Changes: - 81d11b3cf1d5d10427b3ee5ac08f3e209d37a97f tint/spirv-reader: cast offset and count args to u32 for ... by Antonio Maiorano <firstname.lastname@example.org> - d3c9e8c0fe6e20ece7664cd502089407a7d3a8fe tint: Fix RemovePhonies with @must_use fns by Ben Clayton <email@example.com> - 9313aab0fdba908ee85068eadac873656ba275e5 tint/reader/wgsl: Remove case_body() by Ben Clayton <firstname.lastname@example.org> - 2fc56a1c637925f76c6f40604283d33f6cf5018c tint: Use std::string_view for diagnostics by Ben Clayton <email@example.com> - 9a56b25a310cb0c40004669136c0b0c6f3edd82f tint/ast: Remove move-constructors for AST nodes by Ben Clayton <firstname.lastname@example.org> - 39d4065653b86a705e1f270d7622566e26865221 Move BindingRemapper and MultiplanarExternalTexture to a ... by dan sinclair <email@example.com> - 0551c4f40fa372272ab93de25ef12e0c722a88b4 Move MSL configuration for `ArrayLengthFromUniform` trans... by dan sinclair <firstname.lastname@example.org> GitOrigin-RevId: 81d11b3cf1d5d10427b3ee5ac08f3e209d37a97f Change-Id: Ia59e348b41c22c73056d8287520a6e3ef02a86cd Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/124381 Kokoro: Kokoro <email@example.com> Reviewed-by: Ben Clayton <firstname.lastname@example.org> Commit-Queue: Ben Clayton <email@example.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
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.