|author||Tint team <firstname.lastname@example.org>||Wed Apr 13 19:19:51 2022 +0000|
|committer||Tint LUCI CQ <email@example.com>||Wed Apr 13 19:19:51 2022 +0000|
Import Tint changes from Dawn Changes: - 2517d99f351f307f0f339dc2c4173ed2e265f17d Fixup kokoro lint issue by dan sinclair <firstname.lastname@example.org> - 4d5723b5e57070448cbc1c832e3bcec0fa741972 Remove fuzzer CPPLINT file. by dan sinclair <email@example.com> - a5f5f5a1aafa781d40fd00ad31f608738e8d68b7 use stamp file for tint_generate_wgsl_corpus by Fumitoshi Ukai <firstname.lastname@example.org> - c85f8d828e717076d750327797f51cd8c5f456ec tint: Fix doxygen failure by Ben Clayton <email@example.com> - f625a6d57e462946f2c38a4a4c611ee1939f4b53 tint: Make GLSL backend consistent with the others by Antonio Maiorano <firstname.lastname@example.org> - b5c46c30ec440899910fdabcafa3b01027bb5e9e tint: spirv writer: add a GeneralImpl to be consistent wi... by Antonio Maiorano <email@example.com> GitOrigin-RevId: 2517d99f351f307f0f339dc2c4173ed2e265f17d Change-Id: I2abe6ee2d1a03d4e28275187dac5c0f88ee0323c Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/86641 Kokoro: Kokoro <firstname.lastname@example.org> Reviewed-by: Ben Clayton <email@example.com> Commit-Queue: Ben Clayton <firstname.lastname@example.org>
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.