[dawn] Remove AllocNoThrow calls without proper error handling. - CommandAllocator had an AllocNoThrow that caused errors not handled all cases: nullptr would be returned, but when writing AdditionalData of size 0, it wouldn't cause an immediate crash and lead to issue much later. - ChunkedCommandSerializer had an AllocNoThrow but just drops the command if it failed, which seems like it could cause issues downstream. Turn it into a regular allocation. Fixed: 516649133 Change-Id: I90d1b19c0838d32b0b47bd1a2d5779967fdc3f25 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/311135 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@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.