|author||Tint team <firstname.lastname@example.org>||Mon Nov 13 12:08:57 2023 +0000|
|committer||Tint LUCI CQ <email@example.com>||Mon Nov 13 12:08:57 2023 +0000|
Import Tint changes from Dawn Changes: - b383cf0629faeda3a75c1a6c8eb5b5859040671d [tint][gn] Hook up tint_info to the build by Ben Clayton <firstname.lastname@example.org> - d8f6206dc6e0f9de2fb30dd9b73f49faf1f65f93 [tint][resolver] Add validation test for @color and @loca... by Ben Clayton <email@example.com> - 570461ecdae1e36c61aa830034506bebb57b6186 [tint][transform] Update CanonicalizeEntryPointIO tests by Ben Clayton <firstname.lastname@example.org> - 0e4aee6e79ee3c5c24d2a34b41b1398cc7a277cb [tint][wgsl] Parse @color by Ben Clayton <email@example.com> - e73b3936268202c1baf069830ab3ef867c9ee681 [tint][msl] Implement chromium_experimental_framebuffer_f... by Ben Clayton <firstname.lastname@example.org> - 7836e1b2d5e834a5eac09c4bcc3b0079e127f081 [tint][resolver] Fix false-positive dual-source-blending ... by Ben Clayton <email@example.com> - 013fd37bcd800eab06da0893a9f3a560d0bc7540 [tint] Fix conflict between two CLs that landed, breaking... by Ben Clayton <firstname.lastname@example.org> - 4348a05e24ea85775b808b0068d97d1648a9f046 [spirv-writer] Support clamp_frag_depth for multiple entr... by James Price <email@example.com> - 2af581505700219f2f7dcfc501b0027215e7c111 [tint][inspector] Reflect the @color attribute by Ben Clayton <firstname.lastname@example.org> - 45f5c607bdcdef17b8c382f8a279bd48490bab0e [tint] Resolve ColorAttribute by Ben Clayton <email@example.com> - c36093e932c33b6269204461ebbf864bd7e717de [tint][wgsl] Add ColorAttribute by Ben Clayton <firstname.lastname@example.org> GitOrigin-RevId: b383cf0629faeda3a75c1a6c8eb5b5859040671d Change-Id: If54ace3ab35b5ed717aed8e90ba81199a70a57dc Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/160340 Reviewed-by: Ben Clayton <email@example.com> Commit-Queue: Ben Clayton <firstname.lastname@example.org> Kokoro: Kokoro <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.