|author||Tint team <email@example.com>||Thu Jul 28 10:10:20 2022 +0000|
|committer||Tint LUCI CQ <firstname.lastname@example.org>||Thu Jul 28 10:10:20 2022 +0000|
Import Tint changes from Dawn Changes: - 3b2ce130b6ea810e881bac3cc9c0ba24a6d03314 Stay within lex'd token bounds. by dan sinclair <email@example.com> - 08659d098db1c66730bfb3185155e5ebbdf266ac tint/ast: Generate ast::TexelFormat from intrinsics.def by Ben Clayton <firstname.lastname@example.org> - fe8e6ee6827ca214ac789765afc1b939f0c2228a tint/ast: Generate ast::BuiltinValue from intrinsics.def by Ben Clayton <email@example.com> - 9a6acc419eb550a46bf77c4174c521ddfc5ad98d tint: Add tint::OverrideId by Ben Clayton <firstname.lastname@example.org> - b2306e27fcc99443e5e73e0109e8bc018c1aae8b Drop line and col in intrinsic file by dan sinclair <email@example.com> - 8dbd4d028073c22594f4457ebd6c806afd439d41 Add storage_class error reporting to generators and trans... by dan sinclair <firstname.lastname@example.org> - f330229de5a135f4430756dd3d244bd1bddae6a4 tint/ast: Rename Builtin to BuiltinValue by Ben Clayton <email@example.com> - f50d56aa05a63b614c49adaab5f3ced3b100ceb1 tint/ast: Generate ast::Extension from intrinsics.def by Ben Clayton <firstname.lastname@example.org> - a1571ac40308b2551eb51201f00819ca49f7120e tint/inspector: Use a std::optional for workgroup_size by Ben Clayton <email@example.com> - a123b892a57598308577be70286abf74f9c17c64 tint/ast: Generate ast::StorageClass from intrinsics.def by Ben Clayton <firstname.lastname@example.org> - bf8ee3549875457ee5019b83923bf0205763cfab const eval of clamp by Antonio Maiorano <email@example.com> - 4de90f0bb158271919658ec169bd9ba24ebb3d0c const eval of atan2 by Antonio Maiorano <firstname.lastname@example.org> GitOrigin-RevId: 3b2ce130b6ea810e881bac3cc9c0ba24a6d03314 Change-Id: I2e50cb137494bd180c00ae9f491767eba5ed5c92 Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/97383 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.