Roll src/third_party/swiftshader 29364a0595bc..d5f462c6ab22 (2 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/29364a0595bc..d5f462c6ab22


git log 29364a0595bc..d5f462c6ab22 --date=short --no-merges --format='%ad %ae %s'
2019-05-29 hliatis@google.com Fire VkFence in vkAcquireImageANDROID
2019-05-29 hliatis@google.com Fix memory leak in vkDestroyImage


Created with:
  gclient setdep -r src/third_party/swiftshader@d5f462c6ab22

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG=chromium:b/133520634,chromium:133346002
TBR=swiftshader-team+autoroll@google.com

Change-Id: I3ba73fa4f9a6c0d3796797c9463ad2c9932be477
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635976Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#664519}

DEPS

@@ -154,7 +154,7 @@ vars = {
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling SwiftShader
   # and whatever else without interference from each other.
-  'swiftshader_revision': '29364a0595bc52a8b80e8c286cf6a373d419b4f6',
+  'swiftshader_revision': 'd5f462c6ab226942bdf149976bd7ce37f86c5496',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling PDFium
   # and whatever else without interference from each other.