The perf tests can use this callback to instrument timer queries to
delineate render pass times on the device.

The new call pattern in the replay looks like this:

    glBindFramebuffer(GL_FRAMEBUFFER, gFramebufferMap[1]);
    OnFramebufferChange(GL_FRAMEBUFFER_OES, gFramebufferMap[1]);

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

The ANGLE repository will house all the scripts needed to build
ANGLE.apk and the developer options are packaged in the APK.

BUG=angleproject:2344

Change-Id: I29090bd91a07546a1d2ccc03a6af19f45ffa3d90
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2079194Reviewed-by: Tim Van Patten <timvp@google.com>
Commit-Queue: Geoff Lang <geofflang@chromium.org>

In gl::ReadPixels(), ValidateReadPixels() will try to
flush staged updates before readPixels. In the case
where a texture was initialized with null RGBA data,
no Framebuffer dirty bits are set, and thus the staged
clear would never be flushed from the staged updates.

1. Add robust init in TextureVk::initImage to ensure
image is initialized.

Test: ./angle_end2end_tests --gtest_filter=\
RobustResourceInitTest*_Vulkan_AllocateNonZeroMemory

2. Update stageSubresourceRobustClear() to
kEmulatedInitColorValue in the case where robust resource
was initialized without full RGBA format to update
init value of robust resource.

Test: texture-attachment-formats.html in
webgl_conformance_vulkan_passthrough_tests.

3. Revert "Suppress Vulkan RobustResourceInit tests."
Revert commit a8e6a463.

Reason for revert: re-enable related robust tests.

Bug: angleproject:4255
Change-Id: I79f20e0c02c2f1b1cd68ab590f0f765229f9e780
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/1985503
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

This introduces an end2end test that makes the same GLES1
calls as Android's default boot animation. The test uses
images of much smaller sizes, but we do the same thing
with the images as the original code (it uses one image as a
mask and moves the other along behind it).

The original default boot animation code can be found here:
https://android.googlesource.com/platform/frameworks/base/+/refs/heads/master/cmds/bootanimation/BootAnimation.cpp#422

This change also implements glTexParameterx since the default boot
animation requires it. This function is part of OES_FIXED_POINT.

This also includes a test to check for int to floating point cast errors
when using GL_TEXTURE_CROP_RECT_OES.

Tests: angle_end2end_tests --gtest_filter=*DefaultBootAnimation*
       angle_end2end_tests
       --gtest_filter=*TextureParameterTest.IntConversionsAndIntBounds*
Bug: angleproject:3644
Change-Id: Ib7e99c9dc1c001c71543d03ea4dd76082192f6a7
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2053506
Commit-Queue: Brandon Schade <b.schade@samsung.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Tobin Ehlis <tobine@google.com>

Started after SwiftShader enabled ASTC in
https://swiftshader-review.googlesource.com/c/SwiftShader/+/41568

Bug: angleproject:4447
Change-Id: I251ff26d4972f17f1f76f8ad1df57dc9c539782c
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2078755Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>

https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/07e1a0a67aee..f13d38f3cd3c


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

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

Bug: None
Tbr: geofflang@google.com
Change-Id: I076b53154399d1d6bf03f7c1def768986d7752cb
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2080041Reviewed-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/Vulkan-ValidationLayers.git/+log/38f68cce445b..8c312ef4c7a9

git log 38f68cce445b..8c312ef4c7a9 --date=short --first-parent --format='%ad %ae %s'
2020-02-27 mark@lunarg.com threading: Remove use of debug report defs
2020-02-27 attilio.provenzano@arm.com tests: Add BP tests for small allocations
2020-02-27 attilio.provenzano@arm.com practices: Add checks for memory allocations
2020-02-27 attilio.provenzano@arm.com tests: Add BP tests for command buffers
2020-02-27 attilio.provenzano@arm.com practices: Add checks for command buffers

Created with:
  gclient setdep -r third_party/vulkan-validation-layers/src@8c312ef4c7a9

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/vulkan-validation-layers-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/+/master/autoroll/README.md

Bug: None
Tbr: geofflang@google.com
Change-Id: I95d6318d381accc38b0c6a8743cb7c2e3bb7927e
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2080039Reviewed-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/4b34ee3de531..05f5e0b34ac8

git log 4b34ee3de531..05f5e0b34ac8 --date=short --first-parent --format='%ad %ae %s'
2020-02-27 jmadill@chromium.org Add codereview.settings.
2020-02-27 amaiorano@google.com Subzero: add support for variadic calls (System V)

Created with:
  gclient setdep -r third_party/SwiftShader@05f5e0b34ac8

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

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

This reverts commit 93e72f5f.

Reason for revert: This is having a negative impact on gfxbench
Manhattan 3.1 tests (20-30%) with only a minor improvement (~4%) in TRex offscreen. Pulling out for now and need to re-evaluate best
solution here.

Original change's description:
> Vulkan:Include precision qualifier in GLSL
> 
> With this initial implementation, it's possible to get precision
> qualifier mis-matches in the generated GLSL 4.50. According to the
> spec this is allowed. From GLSLangSpec 4.50 section 4.7 "Precision and
> Precision Qualifiers":
> 
> For the purposes of determining if an output from one shader stage
> matches an input of the next stage, the precision qualifier need not
> match.
> 
> However, when converted to SPIR-V and run through the shader validation
> any mismatches will cause shader validation errors. Initially just
> ignoring those errors with this commit.
> 
> Bug: angleproject:3078
> Change-Id: Ia2b04f90f0a7b6b1302c1b1b3e32bcfd8db9ed49
> Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2057749
> Reviewed-by: Jamie Madill <jmadill@chromium.org>
> Reviewed-by: Tobin Ehlis <tobine@google.com>
> Reviewed-by: Tim Van Patten <timvp@google.com>
> Commit-Queue: Tobin Ehlis <tobine@google.com>

TBR=tobine@google.com,timvp@google.com,jmadill@chromium.org

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

Bug: angleproject:3078
Change-Id: I84984e2a963bde573f0f1de585001ceb83623c89
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2079334Reviewed-by: Tobin Ehlis <tobine@google.com>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>

This reverts commit bab2b3de.

Reason for revert:
A fixed clang version has been rolled in, so this flag should no longer
be necessary.

Original change's description:
> Vulkan: Disable global merge for volk
>
> This optimization pass breaks the build by exporting volk's internal
> binding symbols from libGLESv2.so. Since the test binary also links
volk,
> this causes a SEGV as the wrong (uninitialized) function pointer is
> called.
>
> This is an LLVM bug and will be fixed upstream:
> https://reviews.llvm.org/D73235
>
> Bug: angleproject:4351
> Change-Id: Iebe0eabd975f8109231df30eef8c9074af8190e9
> Reviewed-on:
https://chromium-review.googlesource.com/c/angle/angle/+/2023910
> Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
> Commit-Queue: Michael Spang <spang@chromium.org>

TBR=spang@chromium.org,syoussefi@chromium.org,jmadill@chromium.org

Bug: angleproject:4351
Change-Id: Ie832d7d42fab7c8360f2d4d548f1708164c60d3f
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2076138
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>

The extension entry point can forward to the ES 3.0 entry point. Needed
for capturing the mutiple draw buffers sample.

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

The test wasn't reserving a large enough buffer when initializing
the vertex data. Fix the test buffer limits.

Bug: angleproject:4430
Change-Id: I4b9a98e1af1cc8088afb871816061d7ee4dd6a2c
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2079153Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

The extension EGL_ANGLE_iosurface_client_buffer adds a new attribute
to the config: EGL_BIND_TO_TEXTURE_TARGET_ANGLE. However, validation
was not checking the extension was present when this attribute was
requested.

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

Lower precision in Vulkan caused off-by-one issues with this test.

BUG=angleproject:4438

Change-Id: I17111a06133ef403be1f0c99321f1dbf8ab6083c
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2078791Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>

Uses CPU copy if the buffer is CPU visible. Also add dirty bit check to avoid repeated conversion on clean data

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

https://swiftshader.googlesource.com/SwiftShader.git/+log/da659b374113..4b34ee3de531

git log da659b374113..4b34ee3de531 --date=short --first-parent --format='%ad %ae %s'
2020-02-27 jmadill@chromium.org Fix comparison of specialization constant keys.
2020-02-26 amaiorano@google.com Subzero: add support for large stacks on Windows
2020-02-26 capn@google.com Build with -Bsymbolic to prevent symbol preemption

Created with:
  gclient setdep -r third_party/SwiftShader@4b34ee3de531

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

Bug: angleproject:4426
Tbr: geofflang@google.com
Change-Id: I11df2c2bb3b1d3f9d2faef9b2e1471f080b7d377
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2076807Reviewed-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/Vulkan-ValidationLayers.git/+log/3f4d08da8897..38f68cce445b

git log 3f4d08da8897..38f68cce445b --date=short --first-parent --format='%ad %ae %s'
2020-02-26 mikes@lunarg.com scripts: Add line diff to generate_source.py

Created with:
  gclient setdep -r third_party/vulkan-validation-layers/src@38f68cce445b

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/vulkan-validation-layers-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/+/master/autoroll/README.md

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

Bug: angleproject:4259
Change-Id: I518db27a1fb50d35f2c784f655d3e7ee40f4bdf2
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2076415Reviewed-by: Ian Elliott <ianelliott@google.com>
Commit-Queue: Ian Elliott <ianelliott@google.com>

Shared libraries have .cr.so extension in Android component builds.
Tests were failing to load the ANGLE libraries with just .so extensions.

Bug: angleproject:4396
Change-Id: I88555c830c49136623ea9da9896f86ea6204f3b1
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2076778Reviewed-by: Yuly Novikov <ynovikov@chromium.org>
Commit-Queue: Yuly Novikov <ynovikov@chromium.org>

As an Android GLES driver on top of Vulkan, ANGLE must pre-rotate
rendering on behalf of the application.  This involves modifying the
vertex shader to multiply gl_Position with a mat2 "rotation matrix".
Not doing so means that SurfaceFlinger (SF) will perform a costly
rotation blit before presenting every image.  Setting
WindowSurfaceVk::mPreTransform to mCurrentTransform tells SF to not do
the blit.

When the surface is rotated 90 or 270 degrees, the width and height
must be swapped for:

- The swapchain images, and for any depth, stencil, and/or multisample
  attachments used with the swapchain image.

- The viewport, scissor, and render area.

Because the Metal back-end shares the TranslatorVulkan, it will define
the same preRotation (mat2) DriverUniform that is used for Vulkan.

Bug: angleproject:3502
Change-Id: I968dbe8869ba0f50de18dd41f1195e847c06b545
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2038272
Commit-Queue: Ian Elliott <ianelliott@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

commit_id_.py is capable of generating the default commit.h.
This makes it so we always take a single path in gn.

Remove the existing commit.h and generate it into the root
generation folder (not the id subfolder) because Android blueprints
can't handle generating into subfolders that don't exist.

Make the <angle_dir> argument capable of taking a filename or
directory name. This allows us to pass the .git/HEAD file which is
a gn input.  Android blueprints require all paths used as input
or output to a script are listed as inputs or outputs in the genrule.

BUG=angleproject:2344

Change-Id: I6600083fc400faf07808316c4a6244d6599df79a
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2074924
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

Includes a short description of the ContextVk command APIs.

Also a few small cleanups to other Vulkan back-end documentation.

Bug: angleproject:4029
Change-Id: I3bd04861f27b718e6a94fdae00644c124452bc62
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2070597
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Courtney Goeltzenleuchter <courtneygo@google.com>

Was attempting to read invalid shader paths.

Noticed when working on trace/replay.

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

With this initial implementation, it's possible to get precision
qualifier mis-matches in the generated GLSL 4.50. According to the
spec this is allowed. From GLSLangSpec 4.50 section 4.7 "Precision and
Precision Qualifiers":

For the purposes of determining if an output from one shader stage
matches an input of the next stage, the precision qualifier need not
match.

However, when converted to SPIR-V and run through the shader validation
any mismatches will cause shader validation errors. Initially just
ignoring those errors with this commit.

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

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

Test: KHR-GLES31.core.layout_binding.sampler2D_layout_binding_texture_FragmentShader

Bug: angleproject:4106
Bug: angleproject:3089
Change-Id: Ia92ee172ae574e50bf1759583e46ffb54f348962
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2072871Reviewed-by: Shahbaz Youssefi <syoussefi@chromium.org>
Commit-Queue: Courtney Goeltzenleuchter <courtneygo@google.com>

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/8910ea5f1c7b..70f888131ede


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

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

Bug: None
Tbr: geofflang@google.com
Change-Id: I9645668cf93574256604db6f7ef1858a8cea6c11
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2073603Reviewed-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/Vulkan-ValidationLayers.git/+log/a09ab94aa920..3f4d08da8897

git log a09ab94aa920..3f4d08da8897 --date=short --first-parent --format='%ad %ae %s'
2020-02-25 mark@lunarg.com tests: Use VkDisplayKHR objects in thread safety validation
2020-02-25 mark@lunarg.com threading: Cover createobject calls for display objects

Created with:
  gclient setdep -r third_party/vulkan-validation-layers/src@3f4d08da8897

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/vulkan-validation-layers-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/+/master/autoroll/README.md

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

This reverts commit 4dc19c38.

Causes a git error during 'gn gen':
  fatal: this operation must be run in a work tree

BUG=chromium:1055991,angleproject:2344

Change-Id: I74dd36d557dcaf1bd1b13264d806a1c6b09e1a56
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2073200Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

GLSL, ESSL, and HLSL translators all had the same code to emulate
precision so migrate that code to base class.
This is a structural change to prepare for honoring precision
qualifiers in the Vulkan translator as well, which is done in a
follow-on commit.

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

They have to be rolled simultaneously due to a breaking change.

https://swiftshader.googlesource.com/SwiftShader.git/+log/214ec337a0b2..da659b374113
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/79f8caf9154a..8910ea5f1c7b

Bug: angleproject:4425
Change-Id: If9b402295375436fcdb344835b65be7d2b55abc7
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2071011
Commit-Queue: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Jamie Madill <jmadill@chromium.org>

We shouldn't need to special case the barrier logic in this function
any more. Instead use the 'onBufferRead' and 'onBufferWrite' APIs.

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

We would often pad incorrectly given the constraints of the max stride.
We shouldn't really be rounding up the buffer size, but we should
instead be adding the max alignment size to the end of the buffer.

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

Bug: angleproject:4029
Bug: angleproject:4429
Change-Id: Ice4ae48a92e376ea916f05d1433a68f3accc09d5
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2071145Reviewed-by: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Courtney Goeltzenleuchter <courtneygo@google.com>
Commit-Queue: Jamie Madill <jmadill@chromium.org>

According to the OpenGL ES 1.1 spec, remove the conditions
of glOrtho validation that n and f must be positive.

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

Build failed on GCC10 with C++17. An #ifdef was added to support both
C++17 and C++14

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

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

This portability feature allows a single T-Rex capture done on Vulkan
to work seamlessly on the ANGLE GL back-end and the WGL-loaded NVIDIA
OpenGL driver.

Previously the uniform locations would not be consistent between ANGLE
and a native driver. And incompatiblities would trigger error messages
between ANGLE back-ends.

Will allow us to compare ANGLE performance vs the native driver using a
capture.

Example captured calls:

    glLinkProgram(gShaderProgramMap[3]);
    UpdateUniformLocation(gShaderProgramMap[3], "s_texture", 0);

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

Use the following names:

 - flushAndBeginRenderPass
 - endRenderPassAndGetCommandBuffer
 - flushAndGetPrimaryCommandBuffer

This clarifies that a flush is part of the method.

Bug: angleproject:4029
Change-Id: I6c870761339ea7aa39c83142200781ba39ad6a4b
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2068129
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Courtney Goeltzenleuchter <courtneygo@google.com>
Reviewed-by: Tim Van Patten <timvp@google.com>

commit_id_.py is capable of generating the default commit.h.
This makes it so we always take a single path in gn.

Remove the existing commit.h and generate it into the root
generation folder (not the id subfolder) because Android blueprints
can't handle generating into subfolders that don't exist.

Make the <angle_dir> argument capable of taking a filename or
directory name. This allows us to pass the .git/HEAD file which is
a gn input.  Android blueprints require all paths used as input
or output to a script are listed as inputs or outputs in the genrule.

BUG=angleproject:2344

Change-Id: Ifd9c8331f421586db6f2c6e17faf3242376e11d0
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2070600Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Geoff Lang <geofflang@chromium.org>