commit | 24860be060ceac45db13f0ba073651e9222af4ec | [log] [tgz] |
---|---|---|
author | Tint team <no-reply@google.com> | Mon Sep 05 15:25:03 2022 +0000 |
committer | Tint LUCI CQ <tint-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 05 15:25:03 2022 +0000 |
tree | 75f016ca2553d5b3417db3a448242f9e389af1f6 | |
parent | e085daf818d243b6716263e7270ead874e06ae26 [diff] |
Import Tint changes from Dawn Changes: - 3740ac6092c82b2c385820fcafb385608f26d240 tint: implement const eval of binary divide by Antonio Maiorano <amaiorano@google.com> - 679cf4f3517b4008ed12ba66bdfd5781a3c72b9c tint: HLSL and GLSL backends now emit 0 for inf and nan by Antonio Maiorano <amaiorano@google.com> - 1741f4443ecb11fdd80a4be550f171f9885a52fa tint: add CheckedDiv for abstract numbers by Antonio Maiorano <amaiorano@google.com> - 89dd52881c644466fc2351e694fd8abaa3acb1fd spirv-reader: Fix for SelectUsingReferenceVariable by Robert Stewart <admin@robertstewart.dev> - 8478dfca563f8b0748422ecea4eafb91ac36a88c tint: improve error message for const eval operator overf... by Antonio Maiorano <amaiorano@google.com> - 863d9edf59ee93e5ee925a675cbe01a800e36dc7 GLSL: Change Add[Spirv]BlockAttribute to support GLSL by Stephen White <senorblanco@chromium.org> - 822de46c74d045fe761c73bebd723f75287984e4 spirv-reader: fix image write texel conversion for scalar... by David Neto <dneto@google.com> - ece807852db8e1e785aa696b3812c7be22182bfd spirv-reader: Fix texel type confusion in loop by Robert Stewart <admin@robertstewart.dev> - 8b30ca3efa5e35ed735c6cfa2b90ef5e0528c840 tint/transform: Fix FoldTrivialSingleUseLet for abstracts by Ben Clayton <bclayton@google.com> - 188be384f779fcecad9c34825b2cd02bd295cb5b spirv-reader: UnwrapRef on image coords by Robert Stewart <admin@robertstewart.dev> - 648bd7b4be1f2943125c370175b5c9b77cf038ec tint: Add TINT_REFLECT() & ForeachField() by Ben Clayton <bclayton@google.com> GitOrigin-RevId: 3740ac6092c82b2c385820fcafb385608f26d240 Change-Id: I92c9a14e18222dfccefbe4a22842f948b991fc4b Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/101280 Kokoro: Kokoro <noreply+kokoro@google.com> Commit-Queue: Ben Clayton <bclayton@google.com> Reviewed-by: Ben Clayton <bclayton@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.