[vulkan] Enqueue fence and increment serial atomically.

- The bug report notes a small window where we could
  theoretically race with a WaitAny on a submitted work
  done future queried and waited on after the serial was
  incremented, but before the fence was actually enqueued.
  This could result in us thinking that the serial
  completed because we use the existence of the fence as
  a signal. By making those things happen at the same time
  w.r.t the list of fences, we ensure that a race can't
  accidentally see the fence missing and assume that that
  serial had completed.

Bug: 536687607
Change-Id: I933b4e02e34081965977642b8496e86eb858925b
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/325975
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Auto-Submit: Loko Kung <lokokung@google.com>

AllocatorMemoryInstrumentationTest: skip test on WARP

We get spurious failures on the bots presumably because some of them are
running an older system WARP version. Skip for now.

Bug: 536069163
Change-Id: I62a8ba32e1892376ba6509b1a43b2211daaf8bb1
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/325596
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Auto-Submit: Antonio Maiorano <amaiorano@google.com>

Fix build errors about implicit conversions

This patch fixes all the build errors about implicit conversions:
- error: implicit conversion increases floating-point precision:
         'const float' to 'double' [-Werror,-Wdouble-promotion]
- error: comparison of integers of different signs:
        'const unsigned int' and 'const int' [-Werror,-Wsign-compare]

Bug: none
Change-Id: Iceda4d9dbca241a244566b8d4db4c8a563e0c22e
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/323595
Commit-Queue: Shao, Jiawei <jiawei.shao@intel.com>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>

Move core type info to a Flag.

Currently we check the type info name for a prefix of `core::` to
determine if a type is core or not. Instead, add a new `kCore` Flag
which is set in all the types in core/type.

Change-Id: If24024088f84ac40b016a79fdaa1a835fa04ce9a
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/324435
Reviewed-by: Ryan Harrison <rharrison@chromium.org>
Reviewed-by: Steven Perron <stevenperron@google.com>
Commit-Queue: Kai Ninomiya <kainino@chromium.org>

[dawn][wire] Replace some raw allocations with HeapArray

Bug: 512465980
Change-Id: I9b2086af4c305ad5df60869df256bc6f7a7d3090
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/304235
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Auto-Submit: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>

GL: implement Feature::TransientAttachments

Implement support for TransientAttachment via Renderbuffers.
This is a partial reland of https://dawn-review.googlesource.com/c/dawn/+/308775
Renderbuffers are only used for texture formats containing depth or stencil.

Bug: 462577182

Change-Id: I92090e92d6e4e1ee1d732ce97d245aae66ea2ef6
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/323915
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Stephen White <senorblanco@chromium.org>

Roll ANGLE from 195369f6675e to b9aa07e9d122 (6 revisions)

https://chromium.googlesource.com/angle/angle.git/+log/195369f6675e..b9aa07e9d122

2026-06-24 cclao@google.com Vulkan: Fix the bug related to queue family global priority
2026-06-24 cclao@google.com Vulkan: Disable supportsGlobalPriority feature for all
2026-06-24 bsheedy@chromium.org Generate gn_isolate_map.pyl
2026-06-24 syoussefi@chromium.org MSL/AST: Handle non-unary/binary expr in loop-forward-progress
2026-06-24 angle-autoroll@skia-public.iam.gserviceaccount.com Roll vulkan-deps from e73c8345b94e to 5481b8c77757 (9 revisions)
2026-06-24 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from e23ff548502b to 3ebaa3a7d74a (745 revisions)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-dawn-autoroll
Please CC angle-team+autoroll@google.com,jrprice@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in ANGLE: https://bugs.chromium.org/p/angleproject/issues/entry
To file a bug in Dawn: https://bugs.chromium.org/p/dawn/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: jrprice@google.com
Change-Id: If768b99981d6b3f3160e02258c363db489c1f430
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/319755
Commit-Queue: dawn-autoroll@skia-public.iam.gserviceaccount.com <dawn-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: dawn-autoroll@skia-public.iam.gserviceaccount.com <dawn-autoroll@skia-public.iam.gserviceaccount.com>

Roll DirectX Shader Compiler from e68e6b1aa7ea to e39cf36f5b2a (2 rev…

…isions)

https://chromium.googlesource.com/external/github.com/microsoft/DirectXShaderCompiler.git/+log/e68e6b1aa7ea..e39cf36f5b2a

2026-06-23 texr@microsoft.com Update ExperimentalNop tests, add instructions for release shader model update (#7994)
2026-06-23 texr@microsoft.com Prevent experimental RDAT on released shader targets (#8534)

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/directx-shader-compiler-dawn
Please CC jrprice@google.com,webgpu-developers@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in DirectX Shader Compiler: https://github.com/microsoft/DirectXShaderCompiler/issues/new/choose
To file a bug in Dawn: https://bugs.chromium.org/p/dawn/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: jrprice@google.com
Change-Id: Ie64a4de9e4415cff972d3df3dd1ac5ec5e32dcd8
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/319455
Bot-Commit: dawn-autoroll@skia-public.iam.gserviceaccount.com <dawn-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: dawn-autoroll@skia-public.iam.gserviceaccount.com <dawn-autoroll@skia-public.iam.gserviceaccount.com>

[infra] CTS roller: add Bot-Commit+1

The CTS roller account should now have permission to use Bot-Commit.
This change should allow CTS rolls to be landed with just one OWNER
review. (Though rolls that fail to complete, e.g. if they time out on
the last iteration, but then end up succeeding after timing out, won't
get the label.)

To make this work we use an explicit list of owners for the submodule so
that rolls must be reviewed by someone, rather than just being ready to
CQ+2 as soon as they're posted.

This will need to be tested after it lands because only the bot can run
with the trusted account that has Bot-Commit permissions.

Bug: 402777879
Change-Id: I48a92e52587908fd1d808703ff57a7ef0aec81a4
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/300675
Commit-Queue: Kai Ninomiya <kainino@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@google.com>

Roll vulkan-deps from 54730b6db79f to 2e62b853b7b5 (17 revisions)

https://chromium.googlesource.com/vulkan-deps.git/+log/54730b6db79f..2e62b853b7b5

Also rolling transitive DEPS:
  https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools/+log/706f1dc8558316213eac02b0611f9cde6fd3d9c5..ff5c50339cc1e9f34f04cb440a3e5fe89db0161d
  https://chromium.googlesource.com/external/github.com/KhronosGroup/Vulkan-ValidationLayers/+log/d72c5f52886913598d4064fe8d03bf8ac471e215..83ca74c8f08431690fc461eadb912015a25217f2

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/vulkan-deps-dawn-autoroll
Please CC kainino@google.com,webgpu-developers@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Dawn: https://bugs.chromium.org/p/dawn/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Bug: None
Tbr: kainino@google.com
Change-Id: I64f4ebb30fecc1a0eea5abd4e8997a675eb1cc99
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/304635
Bot-Commit: dawn-autoroll@skia-public.iam.gserviceaccount.com <dawn-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: dawn-autoroll@skia-public.iam.gserviceaccount.com <dawn-autoroll@skia-public.iam.gserviceaccount.com>