Skip emitting barriers from MapAsync Emitting a barrier from BufferVk::MapAsyncImpl() should never be necessary due to TransitionMappableBuffersEagerly(). If the buffer hasn't been used on GPU in commands for next submit then a previous eager transition already emitted the required barrier. If the buffer is used on GPU for the next submit then the eager transition will emit the required barrier before vkQueueSubmit() and MapAsync() already waits on completion. Bug: 425472913, 460180744 Change-Id: I584b038101f340ad37a70ee975c8d05f703bcaae Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/270034 Commit-Queue: Kyle Charbonneau <kylechar@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
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.h version that Dawn implements.webgpu.h.Helpful links:
Developer documentation:
User documentation: (TODO, figure out what overlaps with the webgpu.h docs)
BSD 3-Clause License, please see LICENSE.
This is not an officially supported Google product.