encounter
/
dawn-cmake
mirror of https://github.com/encounter/dawn-cmake.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
CMake-only fork of https://dawn.googlesource.com/dawn with cleaned, vendored dependencies
999 Commits 2 Branches 0 Tags 145 MiB
C++ 59.9%
HLSL 18.2%
GLSL 17.3%
Go 2.1%
Objective-C++ 0.8%
Other 1.6%
Go to file
dan sinclair c7f51b7d3c ast: Support decoration kind hierarchies 
Instead of just having a single `DecorationKind` for the first
derivation from `Decoration`, have a `DecorationKind` for every
decoration type.

Add `Decoration::IsKind()` to test whether the decoration is of, or
derives from the given kind.

Note, this change is originally by bclayton@ from
https://dawn-review.googlesource.com/c/tint/+/33201

R=bclayton@google.com

Bug: tint:287
Change-Id: I69b51dfaa3f82ef4d61cda383b2f98f401013429
Reviewed-on: https://dawn-review.googlesource.com/c/tint/+/33280
Commit-Queue: dan sinclair <dsinclair@chromium.org>
Commit-Queue: Ben Clayton <bclayton@google.com>
Auto-Submit: dan sinclair <dsinclair@chromium.org>
Reviewed-by: Ben Clayton <bclayton@google.com>
 		2020-11-18 19:33:30 +00:00
build_overrides Remove binutils from DEPS and pull in changes to build.gni from Dawn 2020-07-28 17:57:53 +00:00
docs [docs] Expand OpImageType documentation 2020-11-11 01:49:28 +00:00
fuzzers Add File & Range information to tint::Source 2020-10-30 20:44:53 +00:00
include/tint Place the namer into the context object. 2020-11-13 18:13:24 +00:00
infra/config Remove refs.cfg. 2020-07-16 19:02:29 +00:00
samples [ast] Add the result_type into the AST dump 2020-11-16 14:46:27 +00:00
src ast: Support decoration kind hierarchies 2020-11-18 19:33:30 +00:00
test [spirv-writer] Support optional trailing return. 2020-11-18 18:25:30 +00:00
third_party Exclude spirv-tools from the all build target. 2020-10-07 15:55:13 +00:00
tools [validation] add error number to invalid member accessor error: v-0007 2020-11-16 14:35:17 +00:00
.clang-format Initial commit 2020-03-02 15:47:43 -05:00
.gitignore Add option and target for generating code cov info 2020-10-27 21:04:59 +00:00
.gn Add in basic BUILD.gn and additional DEPS 2020-04-08 20:40:25 +00:00
BUILD.gn spirv-reader: Add (handle) Usage abstraction 2020-11-17 18:32:18 +00:00
CMakeLists.txt Add option and target for generating code cov info 2020-10-27 21:04:59 +00:00
CODE_OF_CONDUCT.md Initial commit 2020-03-02 15:47:43 -05:00
CONTRIBUTING.md Fixup the contributing file. 2020-04-06 18:43:20 +00:00
CPPLINT.cfg Adding PRESUBMIT.py with a bunch of checks turned on 2020-06-03 13:41:41 +00:00
DEPS Stop setting mac_xcode_version in DEPS 2020-11-16 21:11:19 +00:00
Doxyfile [wgsl-reader][wgsl-writer] Support new sampled texture syntax. 2020-11-04 19:03:21 +00:00
LICENSE Initial commit 2020-03-02 15:47:43 -05:00
PRESUBMIT.py Add language check 2020-11-16 15:01:27 +00:00
README.md One command per line 2020-10-30 15:03:21 +00:00
standalone.gclient Convert dependency management to using gclient 2020-03-05 15:58:27 +00:00
tint_overrides_with_defaults.gni Change the default for BUILD.gn to build all the modules 2020-07-30 18:44:04 +00:00

README.md

Tint

Tint is a compiler for the WebGPU Shader Language (WGSL).

This is not an officially supported Google product.

Requirements

  • Git
  • CMake (3.10.2 or later)
  • Ninja (or other build tool)
  • Python, for fetching dependencies
  • depot_tools in your path

Build options

  • 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)

Building

Tint uses Chromium dependency management so you need to install depot_tools and add it to your PATH.

Getting source & dependencies

# 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

Compiling using CMake + Ninja

mkdir -p out/Debug
cd out/Debug
cmake -GNinja ../..
ninja # or autoninja

Compiling using CMake + make

mkdir -p out/Debug
cd out/Debug
cmake ../..
make # -j N for N-way parallel build

Compiling using gn + ninja

mkdir -p out/Debug
gn gen out/Debug
autoninja -C out/Debug

Fuzzers on MacOS

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.

Checking [chromium-style] issues in CMake builds

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

Issues

Please file any issues or feature requests at https://bugs.chromium.org/p/tint/issues/entry

Contributing

Please see the CONTRIBUTING and CODE_OF_CONDUCT files on how to contribute to Tint.