[DawnLPM] Fix non-deterministic dependency cycle This CL removes the hacky copies that were required to work around `get_target_outputs` from a `proto_library` which caused [1]. The dependency cycle could pop up because a cached obj file could reference a protobuf header which could reference that cached obj file: dawn_lpm_proto.lib -> dawn_lpm_autogen.pb.obj -> gen/third_party/dawn/src/dawn/fuzzers/lpmfuzz/dawn_custom_lpm.pb.h -> obj/third_party/dawn/src/dawn/fuzzers/dawn_lpm_proto.lib [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1455317#c11 Bug: chromium:1455317 Change-Id: Icc092f3d1ba8c53d53f4a3eeb57f8ee733130040 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/152500 Commit-Queue: Brendon Tiszka <tiszka@chromium.org> Kokoro: Kokoro <noreply+kokoro@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Ben Clayton <bclayton@google.com>
Dawn is an open-source and cross-platform implementation of the work-in-progress 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)
(TODO)
Apache 2.0 Public License, please see LICENSE.
This is not an officially supported Google product.