"The CMakeSettings.json file contains information that specifies how Visual Studio should interact with CMake to build a project for a specified platform"

More information can be found here:
https://docs.microsoft.com/en-us/cpp/build/cmakesettings-reference?view=vs-2019

Bug: b/139189696
Change-Id: Ib2d6a79ad997b39538d49e17c3362818b8deaac4
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35091Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

As LValue<T> overloads operator&(), there's no sensible way to get the address of the reactor type.

This is handy for storing a pointer to an Array or LValue in a field.

Bug: b/133213304
Change-Id: I950ee312005bc57187129f009578b8715973804a
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33357Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

https://github.com/KhronosGroup/Vulkan-Headers
revision 4d49d5ced52e1ba1fe5d403726ad8291c1266d97
tag v1.1.111

Bug: b/129792032
Change-Id: Ia4e581160c4612aca44971390b31c7a497b98cfc
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/32968
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

Bug: b/139184291
Change-Id: Iab77a5ac5894aec60fc70f2630b6d2a2b232d253
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/30435Reviewed-by: Ben Clayton <bclayton@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

For Vulkan we must support all blittable formats natively, so there's
no fallback to C++ code. Also, if by error an unsupported format is
used we don't have to immediately abort routine generation but can
continue with something that's benign.

This change simplifies the code, makes it more readable/maintainable,
and marks other formats as unsupported instead of unimplemented.

Bug: b/138944025
Bug: b/131243109
Change-Id: I4d246cdd280c5a352f18341996c92111a5144d96
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34588
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

R16_SNORM, R16_UNORM, and R16G16_SNORM are required for computing cube
corner pixels for decompressed EAC formats.

Bug: b/138944025
Change-Id: I35a4d448e04bba7abc0e34250d153affe7fb1db5
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34829
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

This does not yet handle rounding correctly, nor are Inf and NaN
input values dealt with.

Note that the Vulkan 1.1.117 spec refers to
https://www.khronos.org/registry/DataFormat/specs/1.2/dataformat.1.2.html#11bitfp
for the specification on the interpretation of 11- and 10-bit floating-
point formats, while that spec itself states that:
"Note that in general conversion from a real number to any
representation may require rounding, truncation and special value
management rules which are beyond the scope of a data format
specification and may be documented in APIs which generate these
formats."

The Vulkan spec however does not document any specific conversion
requirement (in contrast, it does for the shared exponent format).

Bug: b/138944025
Change-Id: If59adfb02f2793f69a028d379a03c05f9a12bd89
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34828
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

Bug: b/138944025
Change-Id: I955bb298fffe8e628a1bba73f4144598eebcdd74
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34788
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

We can avoid calling transcendental functions by manipulating the
IEEE-754 representation of the single-precision floating point values.

This implementation produces results identical to the reference code.

Bug: b/138944025
Change-Id: I95faf7e80d0604be115dd1b8dfec72f3b8ece841
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34748
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

log() was used instead of log2().

Also replace pow(2.0f, x) with the equivalent exp2(x), and remove
overloaded functions from Math.hpp which are guaranteed by C++11.

Bug: b/138944025
Change-Id: I9e87ee9b2afd8791a40dd3e73191e1ed0740acf5
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34668
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

Change-Id: I8c631f3b956d206cc1377c1d38c93f418afc20fd
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34988Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Chris Forbes <chrisforbes@google.com>
Presubmit-Ready: Chris Forbes <chrisforbes@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

Without this, the ICD version is stuck at 1, and the loader refuses to
expose functions such as vkCreateWin32SurfaceKHR.

Bug: b/139184291
Bug: b/125405086
Change-Id: I8f11d1df4c5e3390fca39edaadf310de4842a3d4
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34913Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>

The debugger attachment dialog uses a .rc file that was missing from the
CMake build. This caused DllMain to segfault, which the application only
observes as a failure to load the DLL.

Bug: b/139189696
Change-Id: I590c50da2410826598e8238e25f69709d80f2389
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34968
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

This is required for Cuttlefish to compile Swiftshader

Change-Id: If34d250ad9556ea753c706c739c2aed277fbaaab
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34948Tested-by: Chris Forbes <chrisforbes@google.com>
Presubmit-Ready: Chris Forbes <chrisforbes@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

This change is needed to ensure that vk_icdXXX entry points
are exported, as expected by Khronos' Vulkan loader.

Change-Id: I25b232eb3a99767072be198621bda91e3f9f9cbe
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33050
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Tested-by: David Turner <digit@google.com>
Presubmit-Ready: David Turner <digit@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

On 64-bit platforms more collisions can be prevented by spreading
the three 32-bit values more widely apart.

Bug: b/137649247
Change-Id: Icf429b4fc5a3d5d4472b346b190e48ac429bf881
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34929
Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Tested-by: Nicolas Capens <nicolascapens@google.com>

Keying off a single size_t is likely to cause collisions, more so when the hash function is simple shift-xors of 3 32-bit integers.

Use a proper cache key comparision and a better hash function while we're at it.

Bug: b/137649247
Change-Id: I1e0deefb0976102714d43dcb9dcedf6aa809bf7f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34909Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Chris Forbes <chrisforbes@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

Bug: b/125909515
Change-Id: Ifc6c04959e1741d470b133b6bbe05670a7151a0f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34848Tested-by: Chris Forbes <chrisforbes@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

Vulkan does not have nested queries, so this was overbuilt. Get rid of
all the list wrangling and just have a single slot in the draw call for
the active occlusion query.

Bug: b/129706526
Change-Id: I30158895e6ef4edefd6e1de85766fb6c88bb528f
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34728
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Tested-by: Chris Forbes <chrisforbes@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Bug: b/134584057
Change-Id: I1574c9017a5d48f69d14732874a8c8b814056aec
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34248Tested-by: Chris Forbes <chrisforbes@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Change-Id: I62deef5e2db5ccf1794f74f400cfe5d04d24f6a1
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34648
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Tested-by: Ben Clayton <bclayton@google.com>

The last-used sampler routine can be reused when both the image and
sampler descriptors are the same. To prevent a match on uninitialized
cache keys we previously initialized them both to nullptr (as well as
the function pointer itself), at the entry of the shader routine.
This change reduces it to just initializing the image descriptor. This
suffices since all image instructions use an image descriptor
(but not all use a sampler descriptor).

Bug: b/137649247
Change-Id: I62112f12a58ddefb6e56bddab8e3fdfa76c5b756
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34628Tested-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

MakeCurrent no longer generates EGL_BAD_SURFACE when the pbuffers are
IOSurfaces. So the documentation has been updated to match.

Bug chromium:987289

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

Micro-optimization as discussed here:
https://swiftshader-review.googlesource.com/c/SwiftShader/+/34528/7/src/Pipeline/SpirvShader.hpp#1257

Change-Id: I0e71f2b5c882b2e65271a2e8f114239a924462f8
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34549Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

Change-Id: I253abead4412eec7e72148c8680be04c64bd2148
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34548Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

This complements the const-cache in 34348.

Timings for the Glass demo running on a i7-4930K:

this change:               24.25 FPS
this change without 34528: 23.02 FPS
parent change (inc 34528): 22.46 FPS

Bug: b/137649247
Change-Id: I206cdaabfaf63da7f67e3cd5f6823f3343b823c8
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34528Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Re-generated Visual Studio projects using build/cmake.sh. Removed/added
changed SPIRV-Tools projects in solution.

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

We previously set this device limit to infinity to avoid having to
clamp the sum of the sampler and shader provided bias values to the
[-maxSamplerLodBias, maxSamplerLodBias] range. Unfortunately infinity
is not supported/allowed by JSON and the android.graphics.cts.VulkanFeaturesTest
tests which parse the output of the vkjson tool produce a failure.

This change works around it by setting maxSamplerLodBias to a finite
value (15, which is very common according to https://vulkan.gpuinfo.org/),
and performing the clamping required by Vulkan 1.1.117 section 15.6.7.
Fortunately this cost only has to be incurred when an optional Bias
operand is used in the SPIR-V image sampling instruction. When an Lod
operand is used, which is mutually exclusive with Bias because the
former is for explicit-lod instructions and the latter for implicit-lod,
no clamping is required because the explicit LOD is not part of this
clamping equation and the sampler LOD bias must already be clamped as
specified by the spec: "The absolute value of mipLodBias must be less
than or equal to VkPhysicalDeviceLimits::maxSamplerLodBias".

Bug: b/138670766
Change-Id: Iebd6a1fef1c993ec86ac8cc38f8d9a992ba9bc47
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34510Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

The MAP_JIT flag is only supported on macOS 10.14 and higher, so mmap()
may fail on older ones.

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

On macOS 10.14 and higher, executables that are code signed with the
"runtime" option cannot execute writable memory by default. They can opt
into this capability by specifying the "com.apple.security.cs.allow-jit"
code signing entitlement and allocating the region with the MAP_JIT flag.

Note this change only affects use of the Subzero backend of Reactor.

Bug: chromium:985816
Change-Id: I7ea213cc2b62b64c85c4c46a0d4f28e0bace5d21
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34509Tested-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>

Fixes build failures seen here:
https://travis-ci.org/paulthomson/build-swiftshader/jobs/565093397

Change-Id: Ie03b1dbbbbbcc586dc4dfc7eba85e0e225012a16
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34456Reviewed-by: Paul Thomson <paulthomson@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Tested-by: Ben Clayton <bclayton@google.com>

Our copy of glslang is not thread safe, so we need to ensure a mutex is
held during GLSL compilation. With shared contexts this was already the
case because we lock a mutex belonging to the shared resource manager
(through es2::getContext()), but using independent contexts in multiple
threads was unsafe.

Use of glReleaseShaderCompiler() was also unsafe, even with shared
contexts, because no lock was taken.

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

The ICD_LIBRARY_PATH variable needs to be double-escaped - once for CMake, and another for the actual .json file.

Bug b/116336664

Change-Id: I8fd68c6a030b689e6432828ec5f1cf938c2a0d45
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34455Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Tested-by: Ben Clayton <bclayton@google.com>

SpecializationInfo was default copy-constructed / assigned, and held a raw pointer to the copy of the VkSpecializationInfo. This struct was deleted in the destructor, trashing any other copies.

Fixes undefined behavior and crashes of a few Vulkan samples.

Bug b/123588002

Change-Id: I7adcec2d51bc357ef5bcee1ec6bdafe9ecd208a7
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34454
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Ben Clayton <bclayton@google.com>

As these are touched by pixel shaders, this is extraordinarily hot code, and the cost of ref-counting by shared_ptr can really impact performance.

As the const cache is updated at well known sync points, the queryConstCache method is safe to return a raw pointer to the routine.

Bug: b/137524292
Bug: b/137649247
Change-Id: I2ae1f159467eb27b918344714cef1963f3b24a45
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34453
Presubmit-Ready: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Alexis Hétu <sugoi@google.com>
Tested-by: Ben Clayton <bclayton@google.com>

Previuously Fuchsia-specific memory allocation logic was trying to deal
with non-page-aligned address returned from zx_vmar_map(), but it's no
longer necessary because zx_vmap_map() is guaranteed to return
page-aligned address. Also it was trying to unmap partial pages, but
zx_vmar_unmap() now requires that len is page-aligned. This change fixes
both issues by removing two redundant zx_vmar_unmap() calls. Also
deallocateExecutable() has been updated to pass page-aligned size to
zx_vmar_unmap().

This CL resolves test failures in some viz_unittests on Fuchsia.

Bug: chromium:961455
Change-Id: Ib53e46af853802679a55dacc8546c3f67a3486c7
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34409Tested-by: Sergey Ulanov <sergeyu@chromium.org>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>

Bug: b/137828018
Change-Id: Ia30de6af925213269768e3123d3f4ecf821624fb
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34468Tested-by: Nicolas Capens <nicolascapens@google.com>
Reviewed-by: Ben Clayton <bclayton@google.com>

This reverts commit 782a9802.

Change-Id: I95f145db0a7e5351407402861d68bcb17289c698
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33818Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Ben Clayton <bclayton@google.com>
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>

* changes:
  Update SPIRV-Tools to 9559cdbd
  Squashed 'third_party/SPIRV-Tools/' changes from d14db341b..9559cdbdf
  Update SPIRV-Headers to e4322e3b
  Squashed 'third_party/SPIRV-Headers/' changes from 79b6681aa..e4322e3be
  Temporarily disable warnings-as-errors
  Kokoro (Windows): Switch to python3

Always use toLLVM() to avoid a compiler warning / error that the function was declared by never used.

Fix the arguments passed to the DebugInfo constructor.

Change-Id: I1df069c028c9bfcf1f8e7f4221ffffd4f0261069
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34329
Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
Reviewed-by: Nicolas Capens <nicolascapens@google.com>
Tested-by: Ben Clayton <bclayton@google.com>