Google Git
Sign in
dawn / dawn / cafc60bd429c56b430afbbe141f7ca108a0c662c
commitcafc60bd429c56b430afbbe141f7ca108a0c662c[log] [tgz]
authorColin Blundell <blundell@chromium.org>Thu Jan 11 17:08:54 2024 +0000
committerDawn LUCI CQ <dawn-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 11 17:08:54 2024 +0000
tree2189a75723b0f07f44868ec5410a1070b318e7b4
parente856861fedf14ff9a480171e7ac69c78d11ae9ab [diff]
[Mac] Separate TextureMTL bare init from init via SharedTextureMemory

TextureMTL::InitializeFromIOSurface() currently is used in two different
flows:
* Bare initialization of a multiplanar Texture
* Initialization from SharedTextureMemory (whether single-planar or
  multiplanar)

We will shortly be reworking the latter significantly to move creation
of the backing Mtl textures from TextureMTL to SharedTextureMemoryMTL.
In preparation, this CL separates these two flows by inlining the bare
initialization of a multiplanar TextureMTL into
InitializeAsInternalTexture(). This entails pulling in code from two
places into a new InitializeAsInternalTexture()
"initialize a multiplanar texture" codepath:

* The code for creating the IOSurface that is currently in
  TextureMTL::Create()
* The code for initializing a multiplanar TextureMTL from an IOSurface
  that is currently in InitializeFromIOSurface()

Followup changes will pull much of
InitializeFromSharedTextureMemoryIOSurface() into
SharedTextureMemoryMTL and modify it for known invariants of
SharedTextureMemoryMTL, so the minimal code duplication created by this
CL is both intentional and temporary.

Change-Id: I0732bc65380b7a2aa9eca24b4f7d25397b78fa80
Bug: dawn:2152, 1493854
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/169181
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
2 files changed
tree: 2189a75723b0f07f44868ec5410a1070b318e7b4
  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. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. AUTHORS
  25. BUILD.bazel
  26. BUILD.gn
  27. CMakeLists.txt
  28. CMakeSettings.json
  29. CODE_OF_CONDUCT.md
  30. codereview.settings
  31. CONTRIBUTING.md
  32. CPPLINT.cfg
  33. DEPS
  34. DIR_METADATA
  35. Doxyfile
  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. 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.