Includes much more state serialization. Notably Vertex Arrays were
missing as well as multiple GL render states. Also fixes many
serialization bugs. For example, we would not be using the correct
client array and pack/unpack state in the mid-execution capture. Also
depth/stencil attachments were missing from the capture.

Also fixes the replay sample to work with non-zero starting frames.

With these fixes we can run mid-execution replay of the T-Rex demo.

Bug: angleproject:3611
Change-Id: I6945eb9b30a5137be996956b43f074a0a750b333
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1895112
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>

- ContextMtl: triangle fan draws should call setupDraw() with original
parameters. Not the modified parameters.
- SurfaceMtl: should initialize metal layer's drawableSize after layer's
creation.
- TextureMtl & FrameBufferMtl: Fix texture copySubImage CPU path
incorrectly copied unflipped area.
- mtl_render_utils: Fix wrong variable name used for trifan compute
pipeline cache table.
- mtl_resources: Fix texture & buffer memory leaks due to missing
ANGLE_MTL_AUTORELEASE.
- mtl_utils: Fix viewport flipping error due to arithmetic between
unsigned & signed values.

These bugs were discovered during dEQP tests running.

Bug: angleproject:2634
Change-Id: Ie01380910ab68a2b876718d9dac0b5b4c41b607c
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1906608
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>

Apple Features Table says BGRA8 is not always available but it turned
out not the case based on response from Apple dev.

Bug: angleproject:2634
Change-Id: I9e3465420f45fcd362cbdd385bb78169463a759d
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1906606
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>

The copySubImage LUMA workaround sets special TEXTURE_SWIZZLE_RGBA
values to work. However, it must reset this parameter back to the
default state after the workaround completes.

Bug: 1022080
Change-Id: I84870f1264311c106ebece1e6a37d5f92a1da28c
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1904627Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Jonah Ryan-Davis <jonahr@google.com>

The issue which reported the need for this workaround only found a
problem on Mac. The failure doesn't happen on other the Linux
OpenGL Intel driver, so it shouldn't be enabled there.

Bug: chromium:1021900, chromium:644669
Change-Id: I65e7462828419aeb9182898f73977ee1c5e72ff3
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1904291Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Austin Eng <enga@chromium.org>

https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/e471df3c9154..f34cdc70ca1b


Created with:
  gclient setdep -r third_party/glslang/src@f34cdc70ca1b

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 jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: I2902d0c568de1c07f2d688982aa6d80389cd7f94
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1905273Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

https://swiftshader.googlesource.com/SwiftShader.git/+log/27a3d31d7a9d..d9ed1c2732ba

git log 27a3d31d7a9d..d9ed1c2732ba --date=short --no-merges --format='%ad %ae %s'
2019-11-07 sugoi@google.com Prevent rasterizing fragments outside the framebuffer

Created with:
  gclient setdep -r third_party/SwiftShader@d9ed1c2732ba

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 jonahr@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/+/master/autoroll/README.md

Bug: angleproject:4060
TBR=jonahr@google.com
Change-Id: I7cd94017d1dedfcab87e599f586396b9900b8d03
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1905274Reviewed-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/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/dc59b4b075e9..041f0a02493d


Created with:
  gclient setdep -r third_party/spirv-tools/src@041f0a02493d

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-angle-autoroll
Please CC jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: I0937fa1cef8e10179104802c47df697d495702de
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1905272Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

This is an unrelated code cleanup. Previously we would only init these
member variables in the gl::State initialization code.

Bug: angleproject:3611
Change-Id: I3aa34958ce5b00542d45ef63e0b32010b2eb3220
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1902188Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

Implementation of GLSL to MSL translator

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

This index file lets us very easily write a generic capture sample.
Previously the dev had to maintain a list of multiple sources files.
Potentially hundreds. By writing the source file list to an index file
we can load this easily in GN as a variable and plug that into the
sources.

Also updates docs.

Bug: angleproject:3611
Change-Id: I69ba961e271d6d13d06ae01c89a0605a6fd725ec
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1902189
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>

This replaces passing gl::Context. Using a gl::State directly will more
easily let the mid-execution replay code pass a mocked gl::State
instead of having to modify the real underlying Context state. For
example when capturing pixel pack and unpack parameters the states
could not be overridden without changing the gl::Context itself.
Similarly when capturing client side data.

Also moves a query parameter info function into queryutils so it can be
accessible to the State-based capture.

Refactoring change only.

Bug: angleproject:3611
Change-Id: I3c064001cfa83ebbb67a2b8fc8b6180491edd215
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899728Reviewed-by: Cody Northrop <cnorthrop@google.com>
Reviewed-by: Tim Van Patten <timvp@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

https://swiftshader.googlesource.com/SwiftShader.git/+log/88264e3e188d..27a3d31d7a9d

git log 88264e3e188d..27a3d31d7a9d --date=short --no-merges --format='%ad %ae %s'
2019-11-06 jonahr@google.com Fix issues presenting MetalSurfaces

Created with:
  gclient setdep -r third_party/SwiftShader@27a3d31d7a9d

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 jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: I6ca25951e73f298519756654d250524ea23a4b61
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1903408Reviewed-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/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/d9fbf0234869..dc59b4b075e9


Created with:
  gclient setdep -r third_party/spirv-tools/src@dc59b4b075e9

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-angle-autoroll
Please CC jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: If778c8f30ee5cfd9b94216905df566505511cef7
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1902367Reviewed-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/external/github.com/KhronosGroup/glslang/+log/5d0e01d9e7f9..e471df3c9154


Created with:
  gclient setdep -r third_party/glslang/src@e471df3c9154

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 jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: I71df38874026822623509b2bbfff0714ef804326
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1902368Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

Was mistakenly outputting UNSIGNED_BYTE. Caused incorrect rendering in
the T-Rex replay.

Bug: angleproject:3611
Change-Id: I91c91cb8b35f5f56cb4cce5b6893cef0fdbf71d8
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1902187Reviewed-by: Cody Northrop <cnorthrop@google.com>
Reviewed-by: Tim Van Patten <timvp@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

Update ImageHelper to be able to copy both the depth and stencil
aspects of a DS image to a buffer. The aspects are copied separately
with the depth data preceding the stencil data.

This allows dEQP-GLES31.functional.stencil_texturing.misc.base_level
test to pass. Added exception for ANDROID VULKAN where test still
fails and new tracking bug (4080) for this case.

Bug: angleproject:3949
Bug: angleproject:4080
Change-Id: Ib6104d7fa9f516154131f3e82161078ba216cfe1
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1897649Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Tobin Ehlis <tobine@google.com>

When getting the data store from a pipeline cache, we do the following
sequence:

1.) Query the amount of data to get.
2.) Create a buffer to hold that data.
3.) Request that amount of pipeline cache data.

This typically works without errors, but we have seen cases where the
amount of pipeline cache data changes between steps (1) and (3). This
leads to the driver returning VK_INCOMPLETE because we requested a
different amount of data than the driver currently has (either too much
or too little). However, getting at least the pipeline cache header is
all that's required, so this isn't necessarily an error:

From the Vulkan spec:
> If pDataSize is less than the maximum size that can be retrieved by
the pipeline cache, at most pDataSize bytes will be written to
pData, and vkGetPipelineCacheData will return VK_INCOMPLETE. Any
data written to pData is valid and can be provided as the
pInitialData member of the VkPipelineCacheCreateInfo structure
passed to vkCreatePipelineCache.

This change will update ANGLE to ignore VK_INCOMPLETE, rather than
treating it as an error.

Bug: angleproject:3988
Test: Android dEQP-GLES2.*
Change-Id: I6518d7cb00c26ae403b58aafa86a600fa7a8504a
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1900009Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Tim Van Patten <timvp@google.com>

We're temporarily using a pre-release version of the provoking vertex
vulkan extension that's causing the layers to complain about unknown
structs. I already skipped two warnings, but missed this one so adding
it. This will temporarily disable the warning until the extension lands
in the header.

Bug: angleproject:4063
Change-Id: Ide7b0b068fca6ea4b3cd60bce35fb56f431e4739
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1900014Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Tobin Ehlis <tobine@google.com>

Set allowClearForRobustResourceInit to true on D3D9 backend,
which fixes clients report issues where unity web app throws
`Fail to create image surface` error on integrated-intel gpu

Bug: chromium:1011627, chromium:1017076
Change-Id: I733434123a8c34671b1a33b87017367baec5623c
TBR=geofflang@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1898701Reviewed-by: Shrek Shao <shrekshao@google.com>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>

Ensure WebGLCompatibilityTest.EnablePixelBufferObjectExtensions functions
in surfaceless mode by creating a framebuffer to do the test glReadPixels
from.

BUG=angleproject:4079

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

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/e0d5544c9864..d9fbf0234869


Created with:
  gclient setdep -r third_party/spirv-tools/src@d9fbf0234869

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-angle-autoroll
Please CC jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: Ice35b534d9ad4d77b3ef25c2ae14bf2bc44b55be
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899844Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

https://swiftshader.googlesource.com/SwiftShader.git/+log/aaa64b76c0b4..88264e3e188d

git log aaa64b76c0b4..88264e3e188d --date=short --no-merges --format='%ad %ae %s'
2019-11-06 swiftshader.regress@gmail.com Regres: Update test lists @ 215bc794
2019-11-05 jonahr@google.com Add VK_EXT_metal_surface extension support
2019-11-05 capn@google.com Update Vulkan CTS testlist

Created with:
  gclient setdep -r third_party/SwiftShader@88264e3e188d

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 jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: I4e8fae15600166d5f268da1ee513ded8a45b2c52
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899845Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

When VK_EXT_LINE_RASTERIZATION or VK_EXT_PROVOKING_VERTEX is present,
createInfo's pNext pointer is set, which caused pEnabledFeatures to
not be set, which ended up causing memory corruption issues.

This change was made to comply with the Vulkan spec, specifically:
"If the pNext chain includes a VkPhysicalDeviceFeatures2 structure,
 then pEnabledFeatures must be NULL"

Since the VkPhysicalDeviceFeatures2 structure is only added to the
pNext member of the createInfo structure in the if statement above,
restoring the else statement solves this issue.

Bug: angleproject:4060
Change-Id: I0688c4297f167fa28e110cd6ee11a11b95282493
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899731Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Tobin Ehlis <tobine@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

These were fixed upstream.

Bug: angleproject:4077 
Change-Id: I656616a111e1703f8a910c27e6be3ec3e918f6ba
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899726Reviewed-by: Jonah Ryan-Davis <jonahr@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/48233ad3d45b..5d0e01d9e7f9


Created with:
  gclient setdep -r third_party/glslang/src@5d0e01d9e7f9

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 jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: If9ae34dc69395f1497c884285791cff87e0d496e
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899361Reviewed-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/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/f1e5cd73f658..e0d5544c9864


Created with:
  gclient setdep -r third_party/spirv-tools/src@e0d5544c9864

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-angle-autoroll
Please CC jonahr@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/+/master/autoroll/README.md

Bug: None
TBR=jonahr@google.com
Change-Id: Iabc14c43ed42e7fe4aac37269808f412cb194baa
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1899209Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

VK_IMAGE_USAGE_STORAGE_BIT is always enabled for vkImage, this
increases memory bandwidth in some platforms.
This CL changes the behavior to enable VK_IMAGE_USAGE_STORAGE_BIT
when necessary.

Bug: angleproject:3904
Test: angle_end2end_tests
Test: angle_deqp_gles2_tests
Change-Id: I8ffd37efa8d99d04328fa6232de0755be3273d9e
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1857799
Commit-Queue: Sunny Sun <sunny.sun@arm.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

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

This CL adds two new extensions:

 * EGL_ANGLE_ggp_stream_descriptor:
    Introduces a new attribute to CreateWindowSurface. Allows the app
    to pass in a stream descriptor to VkCreateSurfaceKHR.
    Mirrors VK_GGP_stream_descriptor_surface.

 * EGL_ANGLE_swap_with_frame_token:
    Introduces a new function 'eglSwapBuffersWithFrameTokenANGLE'. This
    allows the app to pass a GGP frame token down to vkQueuePresentKHR.
    Mirrors VK_GGP_frame_token.

Bug: angleproject:4078
Change-Id: I4313ac4c264e68999905049f661bc64b44f72fab
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1897315
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>

Add extension string to registry
Add extension flag to EGL and Vulkan Displays

Bug: angleproject:3960
Test: dEQP-EGL.functional.surfaceless_context.*
      angle_end2end_tests --gtest_filter=EGLSurfacelessContextTest*
Change-Id: Id17916f1f636454af395b7bc92892dcf8fc93e54
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1885075
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

Our current fence wait time is triggering timeouts while running with
SwiftShader. However, it's possible for a 'real' application to hit a
timeout also with a large enough workload. This change increases the
timeout to something large enough for us to avoid most timeouts and
instead rely on the OS's detection and recovery mechanism (e.g., Windows
TDR).

We will continue to investigate improving ANGLE's command timeout
handling mechanism.

Bug: angleproject:4043
Test: CQ
Change-Id: I3a32174d1d794806fef1971806797683b6b3f0b2
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1897648
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

Print out EGL vendor, version, clients, clent extensions, display extensions
Print GL vendor, version, renderer, shader, extensions
Prints each EGL config ID and its attributes
Just Vulkan based information. D3D and GL can be enabled.

Bug: angleproject:4039
Test: angle_end2end_tests --gtest_filter=EGLPrintEGLinfoTest*
Change-Id: I103a22eacb2eb14547d7908f93eeeca5434c5e66
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1879492
Commit-Queue: Jeff Vigil <j.vigil@samsung.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

Functions have to be added to the end of the list to prevent breaking
EGL on Android.

Bug: angleproject:2634
Change-Id: I19705144d8ab873c13891038f840b9fc96a79103
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1897646
Commit-Queue: Tim Van Patten <timvp@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

These values are accessible already from the Surface state. Sometimes
they don't apply (e.g. GGP). Remove them to keep the code clearer.
Updates the offscreen surface constructor to pull width and height from
the attributes map instead of using parameters. Otherwise they weren't
used.

Refactoring change only.

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

We're temporarily using a pre-release version of the provoking vertex
vulkan extension that's causing the layers to complain about unknown
structs. Temporarily disable these warnings until the extension lands
in the header.

Bug: angleproject:4063
Change-Id: Ia441ddef21bfcca9bb1b46f25a009eb469e8f1fc
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1895326Reviewed-by: Tim Van Patten <timvp@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Tobin Ehlis <tobine@google.com>

https://swiftshader.googlesource.com/SwiftShader.git/+log/fda994c63075..aaa64b76c0b4

git log fda994c63075..aaa64b76c0b4 --date=short --no-merges --format='%ad %ae %s'
2019-11-01 amaiorano@google.com Modify Blitter to implement FunctionT
2019-11-01 amaiorano@google.com Modify SetupRoutine to implement FunctionT
2019-11-01 amaiorano@google.com Modify PixelRoutine to implement FunctionT
2019-11-01 amaiorano@google.com Modify VertexRoutine to implement FunctionT
2019-11-01 amaiorano@google.com ReactorUnitTests: use FunctionT
2019-11-01 amaiorano@google.com Reactor: add type-safe FunctionT and RoutineT
2019-11-01 natsu@google.com Allow concurrent eglSwapBuffers() with same display but different surfaces
2019-11-01 natsu@google.com Move egl locking code from main.cpp to libEGL.cpp

Created with:
  gclient setdep -r third_party/SwiftShader@aaa64b76c0b4

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 ynovikov@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/+/master/autoroll/README.md

Bug: None
TBR=ynovikov@google.com
Change-Id: I3f139b83f7f77beb913ee2dca988d7cfe98a01ef
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1896150Reviewed-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/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/618ee509421f..f1e5cd73f658


Created with:
  gclient setdep -r third_party/spirv-tools/src@f1e5cd73f658

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/spirv-tools-angle-autoroll
Please CC ynovikov@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/+/master/autoroll/README.md

Bug: None
TBR=ynovikov@google.com
Change-Id: I810ffee83153c8dd880d2e3a1fa4db2b23092f8e
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1896148Reviewed-by: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: angle-autoroll <angle-autoroll@skia-public.iam.gserviceaccount.com>

Mid-execution replay starts the replay from a specific start frame
instead of frame 0. Integration tests will then run between the start
and end frames. This lets us make much smaller reproduction cases from
large benchmarks or applications.

We implement mid-execution replay via a cpp "Setup" function. The
replay test will run the setup function before the starting frame. Test
execution proceeds normally after setup.

Currently we do not implement mid-execution capture. We run capture on
all frames. Including frames before the start frame. We do this to
intercept compiled shaders and programs for easier caching. This could
be changed in the future to also start capture mid-execution. Mid-
execution capture might require using ProgramBinary calls to capture
shader and program data.

Many captures are unimplemented. Several comments indicate missing
functionality. There's a lot we can add as we explore replaying more
complex applications and higher GL versions. We will also need some
kind of state reset functionality so we can run the replay in a loop.

Bug: angleproject:3611
Change-Id: I51841fc1a64e3622c34e49c85ed8919a9a7c0b20
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1689329
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>

Was used in the mip map ANGLE sample. Add a new helper function that we
can use for multiple captures.

Bug: angleproject:3611
Change-Id: I430ce0089df4ce81ba2ca2ad64c0c206b59397b2
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1894144
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Tim Van Patten <timvp@google.com>