CMake-only fork of https://dawn.googlesource.com/dawn with cleaned, vendored dependencies
Go to file
dan sinclair 479dc6b7eb Enable build/header_guard
This CL enables the build/header_guard lint check. The existing headers
which failed the check were updated, missing headers added. An exclusion
file for the generator templates was added as well.

Bug: dawn:1339
Change-Id: If572e460179ad501293d5d6cf01e0ea900daa979
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/86207
Reviewed-by: Ben Clayton <bclayton@google.com>
Auto-Submit: Dan Sinclair <dsinclair@chromium.org>
Commit-Queue: Dan Sinclair <dsinclair@chromium.org>
2022-04-11 18:30:50 +00:00
.vscode .vscode/tasks.json - Add 'cmake gen' 2022-04-07 19:22:21 +00:00
build_overrides Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
docs tint: Standardize the way we forward-declare 2022-04-11 14:37:21 +00:00
generator Enable build/header_guard 2022-04-11 18:30:50 +00:00
include Enable build/header_guard 2022-04-11 18:30:50 +00:00
infra CMake: Fix sanitizer builds 2022-04-08 18:08:36 +00:00
scripts Add compute pipeline cache key generation for Vulkan. 2022-04-09 00:10:08 +00:00
src Enable build/header_guard 2022-04-11 18:30:50 +00:00
test Normalize all line endings to LF 2022-04-08 14:18:28 +00:00
third_party CMake: Add support with Swiftshader with DAWN_ENABLE_SWIFTSHADER 2022-04-11 16:48:43 +00:00
tools tools: Add src/cts/result 2022-04-11 11:03:10 +00:00
webgpu-cts Unskip some CTS tests using the new harness 2022-03-28 18:13:22 +00:00
.clang-format Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
.gitattributes Normalize all line endings to LF 2022-04-08 14:18:28 +00:00
.gitignore tools: Replace copy-pasta scripts 2022-04-07 18:26:45 +00:00
.gn build: Update tint to use C++17. 2022-01-06 09:23:11 +00:00
AUTHORS Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
AUTHORS.dawn Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
AUTHORS.tint Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
BUILD.gn Move samples/ under src/dawn/samples/ 2022-04-11 16:40:00 +00:00
CMakeLists.txt CMake: Add support with Swiftshader with DAWN_ENABLE_SWIFTSHADER 2022-04-11 16:48:43 +00:00
CMakeSettings.json Normalize all line endings to LF 2022-04-08 14:18:28 +00:00
CODE_OF_CONDUCT.md Initial commit 2020-03-02 15:47:43 -05:00
CONTRIBUTING.md Combine contributing files. 2022-04-10 22:14:00 +00:00
CPPLINT.cfg Adding PRESUBMIT.py with a bunch of checks turned on 2020-06-03 13:41:41 +00:00
DEPS Roll vulkan-deps from 60e6ec01372a to ca8ce3e715c2 (1 revision) 2022-04-11 15:49:10 +00:00
DIR_METADATA Move metadata in OWNERS files to DIR_METADATA files 2021-02-04 01:26:43 +00:00
Doxyfile builtins: Add countLeadingZeros 2022-02-22 23:13:39 +00:00
LICENSE Fix google3 license related issues 2021-12-02 21:25:58 +00:00
OWNERS Add top-level OWNERS and scope Tint owners more tightly. 2022-04-07 17:59:14 +00:00
PRESUBMIT.py Create more targeted CPPLINT.cfg files. 2022-04-11 13:05:40 +00:00
PRESUBMIT.py.dawn Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
PRESUBMIT.py.tint Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
README.chromium Add component to OWNERS and fixup repo URL in README.chromium 2018-09-25 20:53:37 +00:00
README.md Remove standalone.gclient 2022-04-07 19:28:44 +00:00
README.md.dawn Merge remote-tracking branch 'tint/main' into HEAD 2022-04-06 15:37:27 -04:00
README.md.tint Remove standalone.gclient 2022-04-07 19:28:44 +00:00
codereview.settings codereview.setings: default to not squashing on git cl upload 2021-03-10 18:35:58 +00:00
dawn.json Revert "Enable Queue, Device labels to be set." 2022-04-05 22:09:43 +00:00
dawn_wire.json Initial Android surface 2022-03-25 13:18:46 +00:00
tint_overrides_with_defaults.gni Normalize DEPS to ease merging with Dawn 2022-03-28 18:01:02 +00:00

README.md

Dawn's logo: a sun rising behind a stylized mountain inspired by the WebGPU logo. The text "Dawn" is written below it.

Dawn, a WebGPU implementation

Dawn is an open-source and cross-platform implementation of the work-in-progress WebGPU standard. More precisely it implements webgpu.h that is a one-to-one mapping with the WebGPU IDL. Dawn is meant to be integrated as part of a larger system and is the underlying implementation of WebGPU in Chromium.

Dawn provides several WebGPU building blocks:

  • WebGPU C/C++ headers that applications and other building blocks use.
    • The webgpu.h version that Dawn implements.
    • A C++ wrapper for the webgpu.h.
  • A "native" implementation of WebGPU using platforms' GPU APIs:
    • D3D12 on Windows 10
    • Metal on macOS and iOS
    • Vulkan on Windows, Linux, ChromeOS, Android and Fuchsia
    • OpenGL as best effort where available
  • A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers

Helpful links:

Documentation table of content

Developer documentation:

User documentation: (TODO, figure out what overlaps with the webgpu.h docs)

Status

(TODO)

License

Apache 2.0 Public License, please see LICENSE.

Disclaimer

This is not an officially supported Google product.

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 scripts/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.

Tint has a process for supporting experimental extensions.