Google Git
Sign in
dawn / dawn / 0de95eebe58cdfa29a00d5affd749669086e9972
commit0de95eebe58cdfa29a00d5affd749669086e9972[log] [tgz]
authorKai Ninomiya <kainino@chromium.org>Mon Mar 24 17:27:25 2025 -0700
committerDawn LUCI CQ <dawn-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Mar 24 17:27:25 2025 -0700
tree419b3fe64f7c6eae2763c6005b44362a8a78ef71
parente987e6615bf2e577a2b835c66576735b8e8eaa88 [diff]
[native] Make mappedAtCreation always return null or a mapped buffer

This is the behavior of the JS API and Dawn Wire. Make Dawn Native
match, by returning nullptr IFF there was an OOM while mapping at
creation. If not, the returned buffer is always mapped (which required
making ErrorBuffer be able to MapAtCreation).

Dawn Native still doesn't quite match the spec; calling device.Destroy()
a second time won't unmap any buffers that were created mappedAtCreation
*after* the first device.Destroy(). But at least the CreateBuffer
invariant is upheld.

Unfortunately, some possible but rare scenarios are not testable
naturally. For these, the DawnFakeBufferOOMForTesting extension allows
injecting simulated OOMs at different points.

Working on this project found several spec issues:
- https://github.com/gpuweb/gpuweb/issues/5101 (tangentially related)
- https://github.com/gpuweb/gpuweb/issues/5102
- https://github.com/gpuweb/gpuweb/issues/5105

Bug: 42241190
Change-Id: If77626a0fc86c7323f776d3781a9bd764068d08b
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/227397
Auto-Submit: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Loko Kung <lokokung@google.com>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
12 files changed
tree: 419b3fe64f7c6eae2763c6005b44362a8a78ef71
  1. .github/
  2. .vscode/
  3. build_overrides/
  4. docs/
  5. generator/
  6. include/
  7. infra/
  8. scripts/
  9. src/
  10. test/
  11. third_party/
  12. tools/
  13. webgpu-cts/
  14. build
  15. buildtools
  16. testing
  17. .bazelrc
  18. .clang-format
  19. .clang-tidy
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .gn
  25. AUTHORS
  26. BUILD.bazel
  27. BUILD.gn
  28. CMakeLists.txt
  29. CMakeSettings.json
  30. CODE_OF_CONDUCT.md
  31. codereview.settings
  32. CONTRIBUTING.md
  33. CPPLINT.cfg
  34. DEPS
  35. DIR_METADATA
  36. go.mod
  37. go.sum
  38. go_presubmit_support.py
  39. LICENSE
  40. OWNERS
  41. PRESUBMIT.py
  42. README.chromium
  43. README.md
  44. WATCHLISTS
  45. WORKSPACE.bazel
README.md

Build Status Matrix Space

Dawn, a WebGPU implementation

Dawn is an open-source and cross-platform implementation of the 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, 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:

Documentation table of content

Developer documentation:

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

License

BSD 3-Clause License, please see LICENSE.

Disclaimer

This is not an officially supported Google product.