Change-Id: Icd01356c6bfaf644112a6ca9cb92b8fc62be5291
Bug: b/149490161
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47769Tested-by: Antonio Maiorano <amaiorano@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

LLVM 11 deprecates the default boolean parameter which indicates whether
vector types are variable-length. Explicitly pass 'false'.

LLVM 11 introduces a FixedVectorType for this as well, which would help
readability, but we're still at LLVM 10.

Bug: b/165000222
Change-Id: I5404cfc8eea9553e15bfb54b2d3278bdf079612f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47768
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Reactor backend: Subzero

Change-Id: I588fa875260f29e32441ac8943f4cff5a4466541
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47670Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

This fixes a bug in the descriptor data where the sample pitch was set
to the layer pitch for array images (it should always be the slice
pitch), and the descriptor's slice pitch (which stores the layer pitch
in case of array images), was taking the sample count into account
twice.

Note that while the image robustness extensions still allow read
operations to return undefined values "if only the sample index was
invalid", so clamping that value would suffice (as currently done in our
OpImageFetch implementation), write operations always have to be no-op.
This change also 'nullifies' the OpImageRead instructions for invalid
sample indices.

Bug: b/163142358
Tests: dEQP-VK.*
Change-Id: I9d816c249e14a17722d29f56015c8dc8cc7d51d4
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47548
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>

Cubemap textures are created with a border, which means that their
size is larger. Their range is also different. Instead of [0, dim-1],
they have a [-1, dim] range. This means that if we copy them starting
at [0, 0] for their full size, we'll overflow at the end, since the
buffer starts at [-1, -1]. This cl prevents going through the fast
copy path when we have a border.

Bug: chromium:1115345
Change-Id: I333acfd6094645231eb111634359d82ed3d5c787
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47668
Presubmit-Ready: Alexis Hétu <sugoi@google.com>
Reviewed-by: Corentin Wallez <cwallez@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>

Reactor backend: Subzero

Change-Id: I1e324936838183d91c0f715fe352ab9413b71e79
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47568Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Block members were getting decorations applied from all previous
block members. For example, in this case:
in InterfaceBlock {
 layout(location = 0) in vec4 in_color_smooth;
 layout(location = 1) in flat vec4 in_color_flat;
 layout(location = 2) in noperspective vec4 in_color_noperspective;
 layout(location = 3) in centroid vec4 in_color_centroid;
}

- the member at location 2 would get decorated with both flat and
  noperspective
- the member at location 3 would get decorated with both flat,
  noperspective and centroid

I added a local variable for the member decorations in order to not
bleed information between block members.

Bug: b/163600604
Change-Id: I6b79609f19ae2f2f48909af929f798a48b4cde34
Tests: dEQP-VK.draw.multiple_interpolation.structured.*
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47649
Presubmit-Ready: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

With the assertion for these tests fixed here:
https://gerrit.khronos.org/#/c/6075/

The *.too_many test passed locally, but not the *.too_many_timeout
test. The reason is that, when a timeout is provided, the acceptable
return value for failing to acquire an image is VK_TIMEOUT, not
VK_NOT_READY. Returning VK_TIMEOUT when a timeout is provided solves
the issue.

Bug: b/162249856
Change-Id: Id2733fec8422aad93a1aa351b481691c69692168
Tests: dEQP-VK.wsi.*.swapchain.acquire.*
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47648
Presubmit-Ready: Alexis Hétu <sugoi@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>

This extension allows the viewport's minimum and maximum depth to be
outside of the 0.0 to 1.0 range:
https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_EXT_depth_range_unrestricted.html

Note that while most extensions don't change the behavior of the logical
device whether they're enabled or not (since they just allow new calls,
enums, or values which are otherwise undefined behavior and implementing
the functionality of the extension is valid as "undefined" behavior),
enabling/disabling this extension does cause an observable difference.

Bug: b/163135814
Tests: dEQP-VK.*depth_range_unrestricted*
Change-Id: I418a2e7226140719af08601d8919f4cdbc7a237c
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47608
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

This cl adds a verification before using the imageView stored
within descriptor sets to make sure they still exist. These
imageView objects are used to make sure images which require
preprocessing (cubemaps and compressed images) are up to date.

The device contains the list of active ImageView objects.

Bug: b/163523811
Bug: b/152227757
Bug: chromium:1110549
Change-Id: I2e2190f2e61296ef3a2e4b699bda885d3a6595d9
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47588Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>

Reactor backend: LLVM

Change-Id: I2bd569ebb5f74fd708e5d0f9598be1f6d445b863
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47468Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>

Bug: b/162315264
Change-Id: I92cca44ad78aea9fcdcb8e0bc0f3c2c1ff28f19f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47508
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>

1D images were being treated as 2D ones with the second coordinate set
to 0.0. It required other workarounds like moving the array layer
coordinate and providing an addressing mode for the second coordinate.
These have been removed, and the texel address calculation now ignores
the second coordinate for 1D images.

Note this doesn't specialize filtering for the 1D case yet, so the
weights for filtering in the v-direction are explicitly zeroed out.

Fixes: b/162858741
Bug: b/134669567
Change-Id: I4684ee0337ac500860e9939087045a953bad813a
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47428
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Instead of reusing the 2D mipmap LOD calculation, this change adds a
separate method for computing the LOD for 1D sampling operations.

This also revealed that we would perform the anisotropic filtering
calculations on 1D sampling operations if enabled, which makes no sense.
This change limits it to 2D sampling only.

Bug: b/134669567
Change-Id: I05dd3fe358eccfcd01ebcff35872f56c6f0b0b70
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47488
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

The array layer coordinate isn't subject to addressing modes like the
other coordinates. There's just one selection computation:
 https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#textures-unnormalized-to-integer
This change eliminates the internally used ADDRESSING_LAYER mode, and
avoids using the 'w' coordinate as the array layer coordinate for 2D
array images (instead exclusively using it for 3D images).

Also, the cube face index is combined with the array layer in case of
cube array images. The division by 6 was eliminated by adjusting the
descriptor 'depth' field instead.

Bug: b/162315264
Change-Id: I4a541697ea265b3ad5b7d7c3a2420c045f46cbbe
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47388
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

- Sort the coordinates and operands in the same order as for the SPIR-V
  instructions.
- Renamed 'q' to 'dRef'.
- Used integer type for offset operands.
- Renamed 'addressingModeY' to 'addressingModeA'. Note this is only used
  by cube array coordinates. 2D array coordinates use 'addressingModeW'
  at the moment.
- Removed array layer coordinate parameter from 3D sampling.
- Added 'dRef' operand for 3D sampling.

Bug: b/162315264
Change-Id: Ia24aa22a57ba5507aa4c8cf617f49f18ccca59c5
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47097
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>

This ensures that if the sample or layer coordinate were not forced to
be in range but the 'valid' mask indicates whether they're in range,
we sample texel 0 instead of potentially outside the image memory.

Note this does not yet validate the sample coordinate.

Bug: b/162419571
Change-Id: I08561862cbf371c1109c8949cd90557110d4ee24
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47228
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Reactor backend: Subzero

Change-Id: Ib5c1f626806c22e49be4e3cfb3286d87ad4bc749
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47448Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Sean Risser <srisser@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

I stumbled across this while bringing up the Chromium build
under Python3. The change should allow the code to work under
both 2 and 3 now.

Bug: chromium:1112479
Change-Id: I5ae0cafdd453a12b53a0fa5392ad46cba60f4ed4
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47308Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>

This extension was never actually implemented. While it has been
promoted to 'core' in Vulkan 1.1, the storageBuffer16BitAccess feature
bit indicates whether or not the implementation supports the
functionality.

Bug: b/162742397
Test: dEQP-VK.info.device_mandatory_features
Change-Id: I3e2871ce09975db3da2ad1f042d6955dbd565479
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47408
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Sean Risser <srisser@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Bug: docs update
Change-Id: I0e0a596456d4c534adb6a8f57455d3cfb9cb65b9
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47289
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Sean Risser <srisser@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Reactor backend: Subzero

Change-Id: I25a37b74498d3a287ed8d78c6a16ca08c3973688
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47328Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Reactor backend: Subzero

Change-Id: I5d78eb4b823a056a07be57932c51391661d4f845
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47268Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>

third_party/subzero is a fork which we are responsible for. Many of the
non-PC words were in files we actually have no use for, so they've been
removed altogether.

Bug: b/162338339
Bug: chromium:1097202
Change-Id: Iaa531dd8788efaf25a640786b78d15d4648b2dd9
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47208Reviewed-by: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>

Swiftshader already counts all the fragments for this feature, it just
needed to be enabled in VkPhysicalDevice.cpp. The occlusion_query tests
that remain unsupported require VK_EXT_host_query_reset. This is
unsupported in SwiftShader as of now, though it is required for Vulkan
1.2 conformance.

Bug: b/148241855
Tests: dEQP-VK.query_pool.occlusion_query.*
Change-Id: Ib03df4225ed49865c648368ebf0547bfc3d117f7
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47148Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Sean Risser <srisser@google.com>

Change-Id: If82af55254be64d6dbe1f9d758f7e2d440b9577a
Bug: b/152028822
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47248Tested-by: Antonio Maiorano <amaiorano@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Change-Id: Iaeb2d94609f8ef6d6c66f537aa3273a59d1610b4
Bug: b/152028822
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47229Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Antonio Maiorano <amaiorano@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Reactor backend: Subzero

Change-Id: I887f6f46e4330ddf0ad317cdb3aad4cdeed9918f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47028Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>

Added a mask to prevent writing to unused outputs

Bug: b/162348737
Change-Id: I72b86cf2f6d0f9f07992cc63bc55fe9e45822e1d
Tests: dEQP-VK.draw.output_location.array.*
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47168
Presubmit-Ready: Alexis Hétu <sugoi@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>

The feature is currently always enabled, so we ignore the creation flag
for now.

Bug: b/159329067
Tests: dEQP-VK.robustness.image_robustness.*
Change-Id: I5385196afd93e3deeaec5713f301af4fed4ef15e
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/46828
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>

VK_EXT_image_robustness requires returning zero on out-of-bounds image
accesses. OpImageFetch was previously merely clamping the coordinates to
be in-bounds.

This change reuses some of the functionality for
VK_SAMPLER_ADDRESS_MODE_CLAMP_TO_BORDER to perform texel replacement.

Bug: b/159329067
Tests: dEQP-VK.robustness.image_robustness.*
Change-Id: I8c00b8de2793b0b7028230cb180d308a4b9b60ec
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47095
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>

VK_EXT_image_robustness requires loads and stores using a pointer
produced by OpImageTexelPointer to be bounds checked. Out-of-bounds
reads must result in [0,0,0,0] or [0,0,0,1] values. We always return
all-zero. Out-of-bounds writes must be ignored.

This also includes the read-modify-write operations performed by atomic
instructions.

Bug: b/159329067
Tests: dEQP-VK.robustness.image_robustness.*
Change-Id: I4f5c2e8ae0bc89e61207fd1f7f1c449a35ca621e
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47069
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>

This change adds CMake targets that setup and build ANGLE by invoking
gclient and gn. The 'angle-setup' target should run only once (if the
.gclient file does not exist), and the 'angle' target will build if any
source file under angle/src is modfied.

The 'angle' target builds libEGL and libGLESv2 into
${CMAKE_BINARY_DIR}/bin-angle. Furthermore, if building PowerVR examples are
enabled (SWIFTSHADER_BUILD_PVR), the PVR output folder,
${CMAKE_BINARY_DIR}/bin, gets copied to ${CMAKE_BINARY_DIR}/bin-angle
first. Finally, a script named 'export-swangle-env.bat/sh' also gets
copied to ${CMAKE_BINARY_DIR}/bin-angle, which sets environment
variables so that the PowerVR examples will run on "SWANGLE" (that is,
on ANGLE on SwiftShaderVK).

Example on Linux:

cd SwiftShader/build
cmake -DSWIFTSHADER_BUILD_PVR=1 -DSWIFTSHADER_BUILD_ANGLE=1 ..
cmake --build . --target angle
source bin-angle/export-swangle-env.sh
./bin-angle/OpenGLESBumpmap

On Windows, run bin-angle\export-swangle-env.bat, and execute the
examples from the bin-angle directory.

Bug: b/152028822
Change-Id: Idd06fb1b6f14b47740692352d353f3a0c9588a90
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47109Tested-by: Antonio Maiorano <amaiorano@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Bug: b/152028822
Change-Id: I13499a0b13f074d876f6038ab776d5de6e27cd3a
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47108Tested-by: Antonio Maiorano <amaiorano@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Bug: b/123642959
Change-Id: I9ee44d6f3ae332f50110a4108481103dca998c77
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/47098
Presubmit-Ready: Alexis Hétu <sugoi@google.com>
Kokoro-Result: kokoro <noreply+kokoro@google.com>
Tested-by: Alexis Hétu <sugoi@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

* changes:
  Update SPIR-V Headers to 979924c8b
  Squashed 'third_party/SPIRV-Headers/' changes from f8bf11a02..979924c8b

* changes:
  Update SPIR-V Tools to 8a5500656
  Squashed 'third_party/SPIRV-Tools/' changes from 55af3902f..8a5500656

Bug: b/161736397
Change-Id: Ia795a1dcf201cc33027f520c0af8d5839d873af9
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/46768Reviewed-by: Alexis Hétu <sugoi@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Caramelli <caramelli.devel@gmail.com>

Changes:
    979924c8b Support SPV_KHR_terminate_invocation (#163)
    7f2ae1193 Merge pull request #162 from vkushwaha-nv/SPV_EXT_shader_atomic_float
    7083cb52e Add changes for SPV_EXT_shader_atomic_float
    308bd0742 Merge pull request #160 from dj2/reg_tint
    5ce353315 Register the Tint compiler
    11d7637e7 Merge pull request #159 from dneto0/fix-quotes
    291d7bf7a spir-v.xml: Use plain ASCII quotes in comment
    ed09fc149 Merge pull request #158 from mkinsner/mkinsner/fpfastmath_allocation_mechanism
    f2d2ca132 Rebuild headers against the previous grammar commit.
    9e2b21a74 Merge pull request #150 from MrSidims/private/MrSidims/UpstreamIntelExt
    7d343e9c0 Apply suggestions
    dfa87b6d4 Add Intel specific definitions from KhronosGroup/SPIRV-LLVM-Translator
    ae6e15156 Header build from previous grammar update.
    8012d1c86 Merge pull request #152 from MrSidims/private/MrSidims/FunctionPointers
    982a08f59 Propose bit allocation mechanism for the FP Fast Math Mode bitfield, following from the mechanism previously added for the loop control bitfield.
    ac638f181 Merge pull request #157 from dneto0/update-example
    1fa1a92e0 Update example to use unified1 headers
    c0df742ec Update headers to SPIR-V 1.5 Revision 3
    375789625 Add a bunch of missing "version" : "None" for ray tracing.
    6300597a6 Rebuild the headers with the fixed grammar file.
    c26f7e838 Add missing "version" : "None" for ShaderCallKHR
    445017dc7 Grammar: The ray-tracing updates were not done in numerical ordering.
    2ad0492fb Discuss generator magic number reservations.
    9995e294c Add SPV_INTEL_function_pointers preview extension

Commands:
    ./third_party/update-spirvheaders.sh

Bug: b/123642959
Change-Id: Icf7b69da64e742a2e43fa6d7d9c42addf0d5aee2

979924c8b Support SPV_KHR_terminate_invocation (#163)
7f2ae1193 Merge pull request #162 from vkushwaha-nv/SPV_EXT_shader_atomic_float
7083cb52e Add changes for SPV_EXT_shader_atomic_float
308bd0742 Merge pull request #160 from dj2/reg_tint
5ce353315 Register the Tint compiler
11d7637e7 Merge pull request #159 from dneto0/fix-quotes
291d7bf7a spir-v.xml: Use plain ASCII quotes in comment
ed09fc149 Merge pull request #158 from mkinsner/mkinsner/fpfastmath_allocation_mechanism
f2d2ca132 Rebuild headers against the previous grammar commit.
9e2b21a74 Merge pull request #150 from MrSidims/private/MrSidims/UpstreamIntelExt
7d343e9c0 Apply suggestions
dfa87b6d4 Add Intel specific definitions from KhronosGroup/SPIRV-LLVM-Translator
ae6e15156 Header build from previous grammar update.
8012d1c86 Merge pull request #152 from MrSidims/private/MrSidims/FunctionPointers
982a08f59 Propose bit allocation mechanism for the FP Fast Math Mode bitfield, following from the mechanism previously added for the loop control bitfield.
ac638f181 Merge pull request #157 from dneto0/update-example
1fa1a92e0 Update example to use unified1 headers
c0df742ec Update headers to SPIR-V 1.5 Revision 3
375789625 Add a bunch of missing "version" : "None" for ray tracing.
6300597a6 Rebuild the headers with the fixed grammar file.
c26f7e838 Add missing "version" : "None" for ShaderCallKHR
445017dc7 Grammar: The ray-tracing updates were not done in numerical ordering.
2ad0492fb Discuss generator magic number reservations.
9995e294c Add SPV_INTEL_function_pointers preview extension

git-subtree-dir: third_party/SPIRV-Headers
git-subtree-split: 979924c8bc839e4cb1b69d03d48398551f369ce7