https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/142cb87f803d..dd69df7f3dac

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: ianelliott@google.com
Change-Id: Ib2c695c9b5b6f6509fd780edfa56ac2cafe5b021
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2572359Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Ian Elliott <ianelliott@google.com>

The tests IndexBufferOffsetTest.UInt16Index and StateChangeTest.
VertexBufferUpdatedAfterDraw can pass 26.20.100.8141 now.

Bug: angleproject:2663
Bug: angleproject:2664
Change-Id: I0324767f5c538879d865cf12304da4625d49bd81
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1166598
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

Test: angle_perftests --gtest_filter="*whatsapp*"
Bug: b/174256233
Change-Id: Ie6abb3beae8e184633005a325c5dce51f0afff40
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574837Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>
Commit-Queue: Paul Thomson <paulthomson@google.com>

Geometry shaders weren't being processed in some of the separable
shader logic. This CL fixes two cases: one in Program and one in
ProgramPipeline.

Bug: angleproject:5409
Change-Id: I19adc5c11a54814d28dd20574a5e038ca9dbd021
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574827
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>

The 3.2 spec and the dEQP tests are quite clear in only requiring
the 'flat' on fragment shader inputs. This restriction remains on
older shader versions.

Bug: angleproject:5409
Change-Id: Icc4b113b404280c2867a3e0bf6f77256a4316bff
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574826
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>

The failed DepthRangeUpdates case can pass on 26.20.100.8141 now.

Bug: angleproject:2844
Change-Id: I1398ab6c4676c1a6bc8f9514b1559ac1e37ed086
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2096337Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

https://swiftshader.googlesource.com/SwiftShader.git/+log/bae138de13ac..7c84426d2abe

2020-12-05 capn@google.com Remove stlport C++11 extensions
2020-12-04 ynovikov@chromium.org Add CQ configuration.
2020-12-04 amaiorano@google.com Add unit test for ENABLE_RR_EMIT_ASM_FILE
2020-12-04 amaiorano@google.com Kokoro: isolate flag enabling for incremental builds
2020-12-04 amaiorano@google.com Kokoro: upgrade Linux build from gcc 7 to 9
2020-12-04 capn@google.com Fix stringification of macro value
2020-12-04 capn@google.com Allow configuring Reactor's anonymous mmap name
2020-12-04 capn@google.com Remove named anonymous mmap for GL/VK allocations

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: geofflang@google.com
Change-Id: I574736428ee405724731a937acdb95e914564f2a
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2575507Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

https://chromium.googlesource.com/chromium/src.git/+log/6991410be08c..bbe26af29575

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Changed dependencies
* build: https://chromium.googlesource.com/chromium/src/build.git/+log/33d5eb7739..b7fc8c9ce5
* testing: https://chromium.googlesource.com/chromium/src/testing/+log/a2515f6c44..95c0c5beb0
* third_party/catapult: https://chromium.googlesource.com/catapult.git/+log/{catapult_..88efddc6a1
No update to Clang.

Bug: None
Tbr: ianelliott@google.com
Change-Id: Ic27236790c9e926431a6b1925a7d191cdb29cfea
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2576445Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

An in-render-pass clear now pauses transform feedback so it wouldn't
contribute to it.  Since it's not possible to resume the transform
feedback in the same render pass (as it needs a memory barrier for its
counter buffer), the render pass is broken after the clear.

Bug: angleproject:5426
Change-Id: I1eaf8c153d076bd912a4a08c65960c12f00341ef
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2573579
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Charlie Lao <cclao@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

- -Wfinal-dtor-non-final-class warns on classes with final dtors but
  not final classes.
- Error messages are better when the class is marked final.
- Fix existing issues in code base

Bug: chromium:999886
Test: no errors building
Change-Id: I62301f2f0b9108b08e0a749fbe261beb36b1996f
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2575923
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>

This is simply done by specifying max_vertices=1.

Bug: angleproject:5411
Change-Id: I50318128cca0e96a8b7c7e5d01165b9ef46b4db8
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574823
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>

https://chromium.googlesource.com/chromium/src.git/+log/78187c025ba6..6991410be08c

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Changed dependencies
* build: https://chromium.googlesource.com/chromium/src/build.git/+log/b85da6c931..33d5eb7739
* testing: https://chromium.googlesource.com/chromium/src/testing/+log/cd2895768d..a2515f6c44
* third_party/catapult: https://chromium.googlesource.com/catapult.git/+log/{catapult_..88efddc6a1
* third_party/libjpeg_turbo: https://chromium.googlesource.com/chromium/deps/libjpeg_turbo.git/+log/d5148db386..bbb828223e
* third_party/protobuf: https://chromium.googlesource.com/chromium/src/third_party/protobuf/+log/1be42a5a07..500b2c2243
* third_party/zlib: https://chromium.googlesource.com/chromium/src/third_party/zlib/+log/9893e506b3..c29ee8c9c3
No update to Clang.

Bug: None
Tbr: ianelliott@google.com
Change-Id: Ie45a97dc9a1523d86e963173c8cbbee2c81be619
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2575916Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

There are a few places that will remain std::unordered_map due to build
or run-time errors, which will need to be evaluated more closely to
determine if they should remain std::unordered_map or if there is
another Abseil data structure that would be more efficient while still
working correctly.

Bug: angleproject:4873
Change-Id: Ib04253e3ad6398e63f4cc2bfe12c0f9e57cb112b
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2558873
Commit-Queue: Tim Van Patten <timvp@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Charlie Lao <cclao@google.com>

When the render pass breaks while transform feedback is active, the
subsequent render passes didn't restart transform feedback because of a
missing dirty bit.

Bug: angleproject:5426
Change-Id: Icee79cbdabbceab96973cea124240ac7ced82d55
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2572878
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Charlie Lao <cclao@google.com>

Bug: angleproject:5406
Change-Id: Ifb7553e87164c204353e1ed94b8d64f5fb4b7206
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574822Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

In order to be able to land SwANGLE in Chromium, this cl adds
suppressions for memory leaks detected by LSAN. Some of these should
be fixed and some are intentional leaks of global variables.

This cl should allow the linux_chromium_asan_rel_ng bot to pass while
using SwANGLE and shouldn't break the win-libfuzzer-asan-rel bot.

Bug: chromium:972686
Bug: angleproject:5377
Change-Id: I7e2336aba43fcfeb95716d6c0aa05caf855134aa
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2575200Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Alexis Hétu <sugoi@chromium.org>

Some apps (possibly those that use Skia) use the extension
GL_CHROMIUM_bind_uniform_location, which is implemented by ANGLE. This
leads to traces that contain calls to functions from this extension,
such as: glBindUniformLocationCHROMIUM. Such traces do not replay on
native GLES drivers, as the extension is not available.

The fix is to disable the GL_CHROMIUM_bind_uniform_location extension
when capturing, so that apps do not use this extension.

Bug: b/174256233
Change-Id: I8c6de9dc958147bcad053cbf89d8727b40f45fbe
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574836
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

Allows shaders that use GS/TS to have input varying variables.

Bug: angleproject:5409
Change-Id: Idfbb725a4eef9e55fdde51d804a891b05dd1daee
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2572879Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

Dirtying the state unnecessarily was causing Vulkan backend to create
new framebuffer objects when it didn't need to.

Bug: b/174700581
Change-Id: I74e0ed51a2c6598ab3dca9a955c247ec97b6856f
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2570201
Commit-Queue: Courtney Goeltzenleuchter <courtneygo@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>

This unifies the variable handling for IO blocks. Previously the
gl_in block we treated as an "in block" similar to an interface block.

Bug: angleproject:5423
Change-Id: Idf2db4c209055fa9ffca567dab39c89464eba156
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2571966Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

This reverts commit 2ded93db.

Reason for revert: Appears to be breaking the ANGLE roll

Original change's description:
> Suppress memory leaks detected by LSAN
>
> In order to be able to land SwANGLE in Chromium, this cl adds
> suppressions for memory leaks detected by LSAN. Some of these
> should be fixed and some are intentional leaks of global
> variables.
>
> This cl should allow the linux_chromium_asan_rel_ng bot to pass
> while using SwANGLE.
>
> Bug: chromium:972686
> Bug: angleproject:5377
> Change-Id: I50a30e74a7d7c799c9dfa4d307792a56cb9d2017
> Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2562748
> Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
> Reviewed-by: Jamie Madill <jmadill@chromium.org>
> Commit-Queue: Alexis Hétu <sugoi@chromium.org>

TBR=sugoi@chromium.org,syoussefi@chromium.org,jmadill@chromium.org,sugoi@google.com

Change-Id: I2ab53f3ab89143ea639424f108c404f884c3aaf9
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:972686
Bug: angleproject:5377
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574796Reviewed-by: Ian Elliott <ianelliott@google.com>
Commit-Queue: Ian Elliott <ianelliott@google.com>

https://chromium.googlesource.com/external/github.com/KhronosGroup/VK-GL-CTS.git/+log/524e5bcfba33..41331850eb21

2020-12-03 alexander.galazin@arm.com Merge vk-gl-cts/vulkan-cts-1.2.5 into vk-gl-cts/master
2020-12-03 ewerness@nvidia.com Shorten the ray so that it can't hit other cells
2020-12-03 ewerness@nvidia.com Only use AABBs for the shader record tests
2020-12-03 rgarcia@igalia.com Enable VK_KHR_ray_tracing_pipeline only if needed
2020-12-03 ewerness@nvidia.com Simplify geometry to reduce AABB precision issues
2020-12-03 rgarcia@igalia.com Test terminateInvocation with frag shader side effects
2020-12-03 michal.opalka@arm.com Fix test using protected features without creating a device with them enabled
2020-12-03 gleese@broadcom.com Fix image cube array tests support checks
2020-12-03 ryan.chen@arm.com Use shader to calculate sample point
2020-12-03 joshua@froggi.es Add tests for VK_EXT_4444_formats
2020-12-03 rgarcia@igalia.com Enable random writes for storage texel buffers
2020-12-03 rgarcia@igalia.com Test reading primitive id from frag shader after tessellation
2020-12-03 paulthomson@google.com Add a batch of GraphicsFuzz tests
2020-12-03 antto.makinen@siru.fi Add a batch of GraphicsFuzz coverage tests
2020-11-27 pdaniell@nvidia.com Update AccessInstance::verifyResult() to support 64-bit types
2020-11-26 Gregory.Grebe@amd.com Add dEQP-VK.pipeline.creation_cache_control.*
2020-11-26 joshua@froggi.es Add support for ABGR texture formats
2020-11-26 alexander.galazin@arm.com Merge vk-gl-cts/vulkan-cts-1.2.4 into vk-gl-cts/master
2020-11-26 rgarcia@igalia.com Force thread count in deferred host operations
2020-11-26 ewerness@nvidia.com Zero out the hit stride for miss SBT tests
2020-11-26 ari.suonpaa@siru.fi Fix validation errors in terminate invocation tests
2020-11-26 tomasz.owczarek@arm.com Add sliced 3D compressed texture test
2020-11-26 pdaniell@nvidia.com Initialize resourceImgLayout before use for all code paths
2020-11-26 marcin.kantoch@amd.com ExtensionUse variable not set for 1D and 3D images
2020-11-26 alexander.galazin@arm.com Merge vk-gl-cts/vulkan-cts-1.2.4 into vk-gl-cts/master
2020-11-26 rgarcia@igalia.com Test vkCmdBindVertexBuffers2EXT with size and offset
2020-11-26 rgarcia@igalia.com Test SPIR-V switch case jumping to the merge block
2020-11-25 gleese@broadcom.com Fixes for image format properties tests
2020-11-25 karolina.palka@mobica.com Add tests for YCbCr chromaFilter linear filtering
2020-11-24 gleese@broadcom.com Add ArrayStride decorations in TerminateInvocation tests
2020-11-24 boris.zanin@mobica.com Add ray tracing extensions to list of known extensions
2020-11-24 alexander.galazin@arm.com Merge vk-gl-cts/vk_khr_ray_tracing into vk-gl-cts/master
2020-11-24 alexander.galazin@arm.com Update glslang, SPIR-V headers, tools
2020-11-24 arkadiusz.sarwa@amd.com Add sparse tests shader_image_atomic_int64
2020-11-24 arkadiusz.sarwa@amd.com Add tests shader_image_atomic_int64 robustness2
2020-11-24 alexander.galazin@arm.com Switch spirv-binaries to Release build
2020-11-20 arkadiusz.sarwa@amd.com Add tests shader_image_atomic_int64 robustness
2020-11-20 arkadiusz.sarwa@amd.com Add tests for VK_EXT_shader_image_atomic_int64
2020-11-20 alexander.galazin@arm.com Update SPIR-V Tools/Headers, glslang

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: ianelliott@google.com,angle-bots+autoroll-info@google.com
Change-Id: Ifb8d1402514edffbaccc84ee83ae288fad881c16
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574175Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

https://chromium.googlesource.com/chromium/src.git/+log/d76e39a75a7a..78187c025ba6

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Changed dependencies
* build: https://chromium.googlesource.com/chromium/src/build.git/+log/796c41e4d2..b85da6c931
* testing: https://chromium.googlesource.com/chromium/src/testing/+log/2a615b18c0..cd2895768d
* third_party/catapult: https://chromium.googlesource.com/catapult.git/+log/{catapult_..d1cf5db415
* tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang.git/+log/8636efe70f..9ec0bb3220
* tools/mb: https://chromium.googlesource.com/chromium/src/tools/mb/+log/4ec098c279..58c3aa7c7b
* tools/skia_goldctl/linux: qmz8kJxTUN_Mt51qpFOU1gn2Es-tf5fUQbm_dwWR4WsC..U9IAKman_wN6alsQfNAUzIasErQFGDvx3wn9o0AQBlEC
* tools/skia_goldctl/mac: VNy9awCiFUEMvA_Yv0NaAUvTu5qcX1KK9w7RAp7kua8C..xF94ClStkjWlYHAlxYXSOCFYEGhzEgxZEwB4zirJIjUC
* tools/skia_goldctl/win: VR4k806B8ASaIGHP_wz13-mO3s-X-NxvU7dSULraOMEC..HYgBDvuNpEKiDYuVIssmP2wgCGe0FS-XKCe18wxZWKwC
No update to Clang.

Bug: angleproject:3354
Tbr: ianelliott@google.com
Change-Id: I29a7ddf57c3f28fc08360df936ae29584e0452f0
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2574157Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

In order to be able to land SwANGLE in Chromium, this cl adds
suppressions for memory leaks detected by LSAN. Some of these
should be fixed and some are intentional leaks of global
variables.

This cl should allow the linux_chromium_asan_rel_ng bot to pass
while using SwANGLE.

Bug: chromium:972686
Bug: angleproject:5377
Change-Id: I50a30e74a7d7c799c9dfa4d307792a56cb9d2017
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2562748Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Alexis Hétu <sugoi@chromium.org>

This reverts commit ff38106d.

Reason for revert: Suspect that this CL may be causing win-angle-rel-32 bot failures

Original change's description:
> Vulkan: Use specialization constant for halfRenderAreaWidth
>
> halfRenderArea is used by fragment shader to adjust gl_FragCoord for
> rotation and yflip compensation. This CL bakes halfRenderAreaWidth into
> shader via specialization constant, thus allow compiler to consolidate
> the calculation into one MAD instruction.
>
> Bug: b/173800146
> Change-Id: Id66301278e3389e2582369b695825e632bccecee
> Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2551541
> Commit-Queue: Charlie Lao <cclao@google.com>
> Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
> Reviewed-by: Tim Van Patten <timvp@google.com>
> Reviewed-by: Jamie Madill <jmadill@chromium.org>

TBR=timvp@google.com,syoussefi@chromium.org,jmadill@chromium.org,cclao@google.com

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: b/173800146
Change-Id: I7bc9966ebbe949f3999d7927afa629dd2e3a4187
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2572801Reviewed-by: Ian Elliott <ianelliott@google.com>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Ian Elliott <ianelliott@google.com>

Bug: chromium:1154759
Change-Id: If31ef7ebecdfa2a0cba91e917870ea0bdfd9b9db
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2570464
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>

https://swiftshader.googlesource.com/SwiftShader.git/+log/bfb211914759..bae138de13ac

2020-12-02 amaiorano@google.com Reactor: add Type* member to Value and remove vtable
2020-12-02 amaiorano@google.com Fix crash from rr::Array with ENABLE_RR_DEBUG_INFO enabled
2020-12-02 natsu@google.com Guard VK_GOOGLE_SAMPLER_FILTERING_PRECISION
2020-12-02 amaiorano@google.com LLVM: add option to emit asm file to aid debugging
2020-12-02 amaiorano@google.com Coroutine: allow a name to be passed in for routine generation
2020-12-02 amaiorano@google.com ReactorUnitTests: use test name as Routine names
2020-12-02 amaiorano@google.com LLVM: store input name in JITRoutine
2020-12-02 amaiorano@google.com Fix FunctionT not forwarding its varargs

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: ianelliott@google.com
Change-Id: Ic8144902a237feefdf7b8d841bbf411f08043ee5
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2570399Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

Add support for labeling of GL objects for debug purposes.

Tests: DebugTest.ObjectLabelsEXT*
Bug: angleproject:5337
Change-Id: I792a27c69395ed62da70c3f619bef71776fba432
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2568711Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Commit-Queue: Mohan Maiya <m.maiya@samsung.com>

This CL can enable and use the VK_EXT_device_memory_report extension.

This is disabled by default.  To enable, link with the required
extension, enable one or both of two features, AND build with the
following GN arg:

  angle_enable_trace = true

The two added  features are:

- logMemoryReportStats provides per-swap statistics
- logMemoryReportCallbacks provides per-callback logging

If either or both of the features are enabled, if the
VK_EXT_device_memory_report extension is available, it is enabled.

Bug: b/173636655
Change-Id: Ic5cf6c06efdb34f2313ef143853b3cc90f55faa5
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2543506
Commit-Queue: Ian Elliott <ianelliott@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Courtney Goeltzenleuchter <courtneygo@google.com>

Geometry shader inputs have an extra array dimension, which can be
unsized as it can be derived from the primitive type.  This change fixes
the grammar to support such arrays.

Additionally, it enables EXT_shader_io_blocks automatically with
EXT_geometry_shader and EXT_tessellation_shader per spec.

Bug: angleproject:3580
Change-Id: Ia7eb3e8be28c2eef2072dbe2a546fa34973104ab
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2568242Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Mohan Maiya <m.maiya@samsung.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

This is a reland of 0f083ab0

Original change's description:
> Reinitialize GL_VENDOR string when GPU switches
>
> We already update the GL_RENDERER string. We should do the same for
> GL_VENDOR so this information is passed along correctly.
>
> Bug: chromium:1152212
> Change-Id: I639700bfebdc9e77ec3c6b41fcd6516e8c32139d
> Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2560824
> Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
> Reviewed-by: Geoff Lang <geofflang@chromium.org>
> Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>

Bug: chromium:1152212
Change-Id: I044313366ce6ce7040e5c203a979b148dcb564dd
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2569364Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>

In preparation for support of primitives generated queries.

Bug: angleproject:5404
Change-Id: Ic123aaff33f8903994ff8fcc9158954ac023ec13
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2562126
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Charlie Lao <cclao@google.com>

Bug: angleproject:5405
Change-Id: I652f2d6d3af4468b9662cdea5d2706d36e118239
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2568550Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

Enables OES/EXT_shader_io_blocks extensions in Vulkan backends.

With shader I/O blocks, the varyings can now be an array of struct (the
block itself) of struct (nested in the block).

This change is missing a number of features.  In particular, if the
shader I/O block has a location decoration in the middle of the block,
that is not handled yet.

Based on changes from m.maiya@samsung.com and jmadill@chromium.org.

Bug: angleproject:3580
Tests: dEQP-GLES31.functional.shaders.linkage.es31.io_block.*
 dEQP-GLES31.functional.separate_shader.validation.es31.io_blocks.*
 dEQP-GLES31.functional.program_interface_query.program_input.*
 dEQP-GLES31.functional.program_interface_query.program_output.*
Change-Id: I593840475d2365ff6c9ce7b2290f5ee462a30dfb
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2567645Reviewed-by: Mohan Maiya <m.maiya@samsung.com>
Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

https://chromium.googlesource.com/chromium/src.git/+log/db49fa80f93d..d76e39a75a7a

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

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Changed dependencies
* build: https://chromium.googlesource.com/chromium/src/build.git/+log/70bbe68c87..796c41e4d2
* testing: https://chromium.googlesource.com/chromium/src/testing/+log/8a83254bed..2a615b18c0
* third_party/abseil-cpp: https://chromium.googlesource.com/chromium/src/third_party/abseil-cpp/+log/5d6094bfbc..1e294aea80
* third_party/catapult: https://chromium.googlesource.com/catapult.git/+log/{catapult_..5537c03942
* tools/mb: https://chromium.googlesource.com/chromium/src/tools/mb/+log/1e9edde7ad..4ec098c279
* tools/memory: https://chromium.googlesource.com/chromium/src/tools/memory/+log/f685c086bd..71214b910d
No update to Clang.

Bug: None
Tbr: ianelliott@google.com
Change-Id: Ie96b014526558dee4b12642f3bd00d61b97921f1
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2568905Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

This reverts commit 0f083ab0.

Reason for revert: Seems to be blocking the ANGLE auto-roller (see: http://anglebug.com/5422)

Original change's description:
> Reinitialize GL_VENDOR string when GPU switches
>
> We already update the GL_RENDERER string. We should do the same for
> GL_VENDOR so this information is passed along correctly.
>
> Bug: chromium:1152212
> Change-Id: I639700bfebdc9e77ec3c6b41fcd6516e8c32139d
> Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2560824
> Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
> Reviewed-by: Geoff Lang <geofflang@chromium.org>
> Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>

TBR=geofflang@chromium.org,syoussefi@chromium.org,jonahr@google.com

Change-Id: I01bbb08946d16cf821f4fb1bfd8b1cade1ab70f1
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: chromium:1152212
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2567460Reviewed-by: Ian Elliott <ianelliott@google.com>
Commit-Queue: Ian Elliott <ianelliott@google.com>

This document shows when and how shader code would hit the
optimization that translates the uniform block into
StructuredBuffer to resolve the slow fxc compiling performace
with dynamic uniform indexing.

Bug: angleproject:3682
Change-Id: I89d94a7e9d812318b9a6cbc470d39ed5ce3e47a0
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2561426Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jiajia Qin <jiajia.qin@intel.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

As ANGLE doesn't redeclare gl_PerVertex, glslang always defines it with:

    gl_Position
    gl_PointSize
    gl_ClipDistance
    gl_CullDistance

The unused members here contribute to varying component limits.  The
last two are unlikely to be used, and the second member is rarely used
as well.

This change keeps it simple and strips the trailing inactive members,
which for all intents and purposes accurately minimizes this struct.

Bug: angleproject:5405
Change-Id: I59c22af4988a3da7b1e428913d0ea13be9031cea
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2562754
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

We already update the GL_RENDERER string. We should do the same for
GL_VENDOR so this information is passed along correctly.

Bug: chromium:1152212
Change-Id: I639700bfebdc9e77ec3c6b41fcd6516e8c32139d
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2560824Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>

This reverts commit b1917fe1.

Reason for revert: Not the root cause. See bug.

Original change's description:
> Revert "Vulkan: Use specialization constant for halfRenderAreaWidth"
>
> This reverts commit ff38106d.
>
> Reason for revert: Speculative revert to clear up AMD. See bug.
>
> Bug: chromium:1154356
>
> Original change's description:
> > Vulkan: Use specialization constant for halfRenderAreaWidth
> >
> > halfRenderArea is used by fragment shader to adjust gl_FragCoord for
> > rotation and yflip compensation. This CL bakes halfRenderAreaWidth into
> > shader via specialization constant, thus allow compiler to consolidate
> > the calculation into one MAD instruction.
> >
> > Bug: b/173800146
> > Change-Id: Id66301278e3389e2582369b695825e632bccecee
> > Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2551541
> > Commit-Queue: Charlie Lao <cclao@google.com>
> > Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
> > Reviewed-by: Tim Van Patten <timvp@google.com>
> > Reviewed-by: Jamie Madill <jmadill@chromium.org>
>
> TBR=timvp@google.com,syoussefi@chromium.org,jmadill@chromium.org,cclao@google.com
>
> Change-Id: Idab612bcad4f179857c41ffc4bf8fa2355fae946
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: b/173800146
> Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2568244
> Reviewed-by: Jamie Madill <jmadill@chromium.org>
> Commit-Queue: Jamie Madill <jmadill@chromium.org>

TBR=timvp@google.com,syoussefi@chromium.org,jmadill@chromium.org,cclao@google.com

# Not skipping CQ checks because this is a reland.

Bug: chromium:1154356
Bug: b/173800146
Change-Id: I5b86bbee8600c6597620f31d8d7b08ca8b3d2d57
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2568246Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>