CMake-only fork of https://dawn.googlesource.com/dawn with cleaned, vendored dependencies
8ab7dbe424
Currently in the middle of some functions, we execute callbacks immediately such as inside Buffer::APIMapAsync(), Device::HandleError() or Queue::Submit(). Firstly, this has risks. The functions might be in a middle of modifying internal states. By triggering callbacks, users might call API functions again which could further modify the internal states unexpectedly or access the states in an inconsistent way. Secondly, upcoming thread safe API which locks the public functions with a mutex might encounter deadlock. Because callbacks might cause re-entrances which would unexpectedly lock the public function again. This CL attempts to limit number of functions that are allowed to trigger callbacks. Other functions that want to trigger callbacks will instead enqueue a request to execute callbacks in the next Device::APITick() call. Currently the functions that will be allowed to trigger callbacks are: - Device::WillDropLastExternalRef() - Device::APITick() - Device::APISetLoggingCallback() - Device::APISetUncapturedErrorCallback() - Device::APISetDeviceLostCallback() Bug: dawn:1672 Change-Id: Iabca00f1b6f8f69eb5e966ffaa43dda5ae20fa8b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/120940 Commit-Queue: Quyen Le <lehoangquyen@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Kokoro: Kokoro <noreply+kokoro@google.com> |
||
|---|---|---|
| .vscode | ||
| build_overrides | ||
| docs | ||
| generator | ||
| include | ||
| infra | ||
| scripts | ||
| src | ||
| test | ||
| third_party | ||
| tools | ||
| webgpu-cts | ||
| .clang-format | ||
| .clang-tidy | ||
| .gitattributes | ||
| .gitignore | ||
| .gn | ||
| AUTHORS | ||
| BUILD.gn | ||
| CMakeLists.txt | ||
| CMakeSettings.json | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CPPLINT.cfg | ||
| DEPS | ||
| DIR_METADATA | ||
| Doxyfile | ||
| LICENSE | ||
| OWNERS | ||
| PRESUBMIT.py | ||
| README.chromium | ||
| README.md | ||
| codereview.settings | ||
| dawn.json | ||
| dawn_wire.json | ||
| go.mod | ||
| go.sum | ||
| go_presubmit_support.py | ||
| tint_overrides_with_defaults.gni | ||
README.md
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.hversion that Dawn implements. - A C++ wrapper for the
webgpu.h.
- The
- A "native" implementation of WebGPU using platforms' GPU APIs: D3D12, Metal, Vulkan and OpenGL. See per API support for more details.
- A client-server implementation of WebGPU for applications that are in a sandbox without access to native drivers
- Tint is a compiler for the WebGPU Shader Language (WGSL) that can be used in standalone to convert shaders from and to WGSL.
Helpful links:
- Dawn bug tracker if you find issues with Dawn.
- Tint bug tracker if you find issues with Tint.
- Dawn's mailing list for other discussions related to Dawn.
- Dawn's source code
- Dawn's Matrix chatroom for live discussion around contributing or using Dawn.
- WebGPU's Matrix chatroom
- Tint mirror for standalone usage.
Documentation table of content
Developer documentation:
- Dawn overview
- Building
- Contributing
- Code of Conduct
- Testing Dawn
- Debugging Dawn
- Dawn's infrastructure
- Dawn errors
- Tint experimental extensions
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.