|author||Jiawei Shao <firstname.lastname@example.org>||Wed Nov 28 02:44:17 2018 +0000|
|committer||Commit Bot service account <email@example.com>||Wed Nov 28 02:44:17 2018 +0000|
Add checks on the texture view used as color or depth stencil attachment This patch adds checks when we set a texture view as color or depth stencil attachments: 1. The mipmap level of the texture view must be 1 as it is limited in D3D12, Metal and Vulkan. 2. The array layer count of the texture view must be 1 as currently we do not plan to support layered rendering in WebGPU. 3. The format of the texture view must be color renderable when it is used as a color attachment. 4. The format of the texture view must be a depth stencil format when it is used as a depth stencil attachment. BUG=dawn:16 TEST=dawn_unittests Change-Id: Ibce3bda20d49a725c26796aa627c5067532761ad Reviewed-on: https://dawn-review.googlesource.com/c/2661 Commit-Queue: Jiawei Shao <firstname.lastname@example.org> Reviewed-by: Kai Ninomiya <email@example.com>
Dawn (formerly NXT) is an open-source and cross-platform implementation of the work-in-progress WebGPU standard. It exposes a C/C++ API that maps almost one-to-one to the WebGPU IDL and can be managed as part of a larger system such as a Web browser.
Dawn provides several WebGPU building blocks:
dawn.json: description of the API used to drive code generators.
examples: examples showing how Dawn is used.
generator: code generator for files produces from
templates: Jinja2 templates for the generator
scripts: scripts to support things like continuous testing, build files, etc.
common: helper code shared between core Dawn libraries and tests/samples
dawn_native: native implementation of WebGPU, one subfolder per backend
dawn_wire: client-server implementation of WebGPU
include: public headers for Dawn
tests: internal Dawn tests
end2end: WebGPU tests performing GPU operations
unittests: unittests and by extension tests not using the GPU
validation: WebGPU validation tests not using the GPU (frontend tests)
utils: helper code to use Dawn used by tests and samples
third_party: directory where dependencies live as well as their buildfiles.
Dawn uses the Chromium build system and dependency management so you need to install depot_tools and add it to the PATH.
On Linux you need to have the
# Install pkg-config on Ubuntu sudo apt-get install pkg-config
Then get the source as follows:
# Clone the repo as "dawn" git clone https://dawn.googlesource.com/dawn dawn && cd dawn # Bootstrap the gclient configuration cp scripts/standalone.gclient .gclient # Fetch external dependencies and toolchains with gclient gclient sync
Then generate build files using
gn args out/Debug or
gn args out/Release. A text editor will appear asking build options, the most common option is
gn args out/Release --list shows all the possible options.
ninja -C out/Release to build dawn and for example
./out/Release/dawn_end2end_tests to run the tests.
Please read and follow CONTRIBUTING.md. Dawn doesn‘t have a formal coding style yet, except what’s defined by our clang format style. Overall try to use the same style and convention as code around your change.
If you find issues with Dawn, please feel free to report them on the bug tracker.
Please see LICENSE.
This is not an officially supported Google product.