[emscripten] Fix cleanup steps in emwgpuWaitAny By making the whole emwgpuWaitAny function async, we shouldn't need Asyncify.handleAsync (which just does runtimeKeepalivePush/Pop). `result` was a Promise, so the `delete` call was not doing anything. Because of `__async: true`, though, we _were_ returning the resolved future ID to webgpu.cpp, so that was already working fine. Also remove the waitAnyPromisesList optimization because it probably creates a re-entrancy problem (for nested WaitAny calls - though I'll note that nested WaitAny calls still don't work after this change). No-Try: true Bug: none Change-Id: I06ff17914b50ad24da254c98789dea3ea821396a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/217094 Reviewed-by: Loko Kung <lokokung@google.com> Commit-Queue: 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.