- 18 Sep, 2019 3 commits
-
-
Jamie Madill authored
This allows the TSAN/ASAN builds to properly locate the library. Makes the fuchsia workaround apply everywhere. Bug: chromium:1000668 Bug: angleproject:3876 Change-Id: Ide2e8527c89c614a648204e953def1f24b702a62 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36468 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Jamie Madill <jmadill@chromium.org> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Chris Forbes authored
dEQP doesn't try to render this format with blending enabled, so we missed the attachment read path. Change-Id: Ib1decc0dbdf1e9895b5ac00b478a65fd717e534c Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36488Tested-by:
Chris Forbes <chrisforbes@google.com> Presubmit-Ready: Chris Forbes <chrisforbes@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Chris Forbes authored
Several weeks ago I did some build system rationalization which subtly broke cuttlefish. Unfortunately nothing screamed very loudly so we didn't notice. - Place the libraries in the correct directory - Use libarect (static lib for this purpose) rather than libui (which is inaccessible to sphal even though the build system will allow it) Bug: b/141209513 Change-Id: I4e9010bfb83686a876968daab8e99df736d4b1e8 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36451Tested-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>
-
- 17 Sep, 2019 1 commit
-
-
SwiftShader Regression Bot authored
Change-Id: Ifc8cf06bcc18d197fd45bb08779342ddc7f20265 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36448 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
- 16 Sep, 2019 6 commits
-
-
Alexis Hetu authored
Bug b/140294254 Test: dEQP-VK.binding_model.* Test: dEQP-VK.glsl.atomic_operations.* Test: dEQP-VK.robustness.vertex_access.* Test: dEQP-VK.synchronization.op.single_queue.* Change-Id: I5f3cd246d93b6550a2ad982f1c838ad9c02d3858 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35789Tested-by:
Alexis Hétu <sugoi@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Alexis Hetu authored
Robust buffer access for vertex inputs/attributes was not implemented. It's fixed in this cl by adding robustBufferAccess to the Context structure, adding a check in Renderer::advanceInstanceAttributes() to prevent advancing a buffer past its end and adding out of bounds checks in VertexRoutine::readStream() This affects dEQP-VK.robustness.vertex_access.* tests, which will be enabled when the vertexPipelineStoresAndAtomics feature is turned on. For now, this change should be noop in test results. Bug b/140294254 b/131224163 Change-Id: Ib4d4cdb73f48495a556b6bd05b1d0e3ce800ad15 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36268Tested-by:
Alexis Hétu <sugoi@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Alexis Hetu authored
Extra vertices are added at the end of the vertex list when processing a batch in order to avoid SIMD width overrun. A single comparison can prevent us from processing these vertices by disabling them in the stores and atomics mask. This would fix the following tests: dEQP-VK.synchronization.op.single_queue.* when enabling the vertexPipelineStoresAndAtomics feature. Note that these tests are affected because they wrongly assume vertices won't be processed more than once. These tests should still get fixed. Bug b/140294254 Change-Id: I04185b899a9770537c3d10bcfd87e00e314582de Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36368 Presubmit-Ready: Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
Alexis Hetu authored
Instead of packing each point in a triangle primitive, tightly pack all point vertices and write them out 3 at a time in the output primitive. This should be roughly twice as fast. Explanation: Currently: Vertices: 0 0 0 1 1 1 2 2 2 ... Processing: 1) 0 0 0 1 2) 0 (cache hit) 3) 0 (cache hit) 2) 1 (cache hit) 3) 1 (cache hit) 4) 1 (cache hit) 5) 2 2 2 3 ... -> We processed 8 vertices to get points 0 1 2 3 New way: 1) 0 1 2 3 -> We processed 4 vertices to get points 0 1 2 3 2) 4 5 6 7 Will affect these tests once vertexPipelineStoresAndAtomics is enabled: dEQP-VK.glsl.atomic_operations.* Note that these tests are affected because they wrongly assume vertices won't be processed more than once. These tests should still get fixed. Bug b/140294254 Change-Id: Idb21085838317db7b7a6630a18de4d7284534429 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36349 Presubmit-Ready: Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
SwiftShader Regression Bot authored
Change-Id: I65ed5dc54a648a148c1cf95546902e64df629bca Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36128 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Chris Forbes <chrisforbes@google.com>
-
Sean Risser authored
While blitting, it's possible to generate a float that is outside the representable values of an integer. Since converting such a float results in undefined behavior, we instead throw an invalid operation error and return without continuing the blit. Bug chromium:1001874 Change-Id: Ic6938adf75176e34021d0ca1404176e4979a3ca6 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36408Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
Sean Risser <srisser@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
- 13 Sep, 2019 3 commits
-
-
Alexis Hetu authored
The Renderer needs to be aligned when allocated, otherwise it leads to all sorts of hard to track issues in the 32 bit version of the library. In this instance, Angle's end to end tests on SwiftShader Vulkan had spurious failures due to having unaligned members in PixelProcessor, which wasn't aligned because it's used as a base class of the Renderer class, which wasn't aligned when allocated. Using an allocator to align the memory fixes the issue. I also did a small cleanup of PixelProcessor::setBlendConstant, as it was a bit hard to debug and changing it this way made it easier to track what was going on. Bug b/140888415 Change-Id: Ie5559642456ee4dcb73f9d07c777349f558879ba Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36248 Presubmit-Ready: Alexis Hétu <sugoi@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
David 'Digit' Turner authored
A previous CL broke the Android build due to the fact that sw::trace() is only defined by System/Debug.hpp on non-Android platforms (while DebugAndroid.hpp defines trace() instead). Use the TRACE() macro instead of calling the function directly. Bug: b/73656151 Change-Id: I85e9f592a43df8bc4dc719b995934bb9c3bfa97f Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36329Tested-by:
David Turner <digit@google.com> Kokoro-Presubmit: David Turner <digit@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Tom Tan authored
src/System/Timer.cpp which was duplicated for Vulkan uses x86 intrinsic __rdtsc to tick count. This intrinsic is not available on ARM and needs to be fixed. This issue broke Windows ARM64 build bot and the same issue was fixed for src/Common/Timer.cpp before (see below links). https://ci.chromium.org/p/chromium/builders/ci/win32-arm64-rel/7763 https://swiftshader-review.googlesource.com/c/SwiftShader/+/23508 Bug: chromium:893460 Change-Id: I48e3673034650a89fead71447d75f4e486ee68b5 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36308 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
- 12 Sep, 2019 6 commits
-
-
David 'Digit' Turner authored
This creates a new helper class to allocate memfd-backed shared memory regions with the Linux kernel. The feature has been supported since at least Linux 3.17, which is sufficient for a large number of desktop Linux and Android devices. However, only recent version of GLibc or the Android C library expose memfd_create(), so keep implementing it as a direct syscall. NOTE: There is a similar function named memfd_create() inside of src/Reactor/ExecutableMemory.cpp, but it is easier to keep them separate for now to avoid introducing subtle dependency issues in the CMakeLists.txt file. This will used in future CLs that implement Vulkan external semaphores and external memory on Linux and Android for SwiftShader. Bug: b/140419396 Change-Id: I378c34760930d8fef7d0659128ededb5227c323f Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35128Reviewed-by:Nicolas Capens <nicolascapens@google.com> Tested-by:
David Turner <digit@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Nicolas Capens authored
C++11 does not have a way to write an infinite or NaN literal, nor does it allow division by zero as a constant expression. Thus we should not accept inf or NaN as a Reactor Float constant, as this would typically indicate a bug, and avoids undefined behavior. This also prevents the issue of the LLVM JIT only taking double values for constructing floating-point constants. During the conversion from single-precision to double, a signaling NaN can become a quiet NaN, thus altering its bit pattern. Hence this assert is also helpful for detecting cases where integers are being reinterpreted as float and then bitcast to integer again, which does not guarantee preserving the integer value. Should infinity and NaN constants be required, methods like infinity(), quiet_NaN(), and signaling_NaN() should be added to the Float class. For cases where binary float data must be preserved exactly, one can construct a Reactor Int value and bitcast as Float. Bug: b/140302841 Change-Id: I72cf7e6fe82913cffcb1e0de282bc6839f65226d Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35868 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
Nicolas Capens authored
Constructing a constant SIMD::Float is not guaranteed to preserve the data's exact bit pattern, but SPIR-V provides 32-bit words representing "the bit pattern for the constant". Thus we must first construct an integer constant, and bitcast to float. Bug: b/140302841 Change-Id: I1a84dab9d1adbdc15f8a3b2fc639c637d2841174 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36208 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
Nicolas Capens authored
All sampler operands are passed through an array of float values. Offset operands are integers, but we were retrieving them from the SPIR-V constant object interpreted as floating-point data, and then creating Float constants from them. This may alter their bit pattern, specifically values corresponding to sNaN may become qNaN. Instead create Reactor integer constants and bitcast them to Float. Bug: b/140302841 Change-Id: I06aceb7b2a97d5f5ce9009f5ba97238602cdc126 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35910 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
Nicolas Capens authored
Reactor Float scalar and vector constants may not fully preserve the bit pattern of the values they were constructed from. Specifically, signaling NaN values (sNaN) may become quiet NaN values (qNaN). Thus they should not be used for storing SPIR-V constant objects to memory. Interpret the data as integer instead. Note Object::constantValue is already a uint32_t array. Bug: b/140302841 Change-Id: Ifd51eec9d2b7adab8fef5de74e2e30d080a28fd5 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35909 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
Nicolas Capens authored
Despite the name, PARAMETER_FLOAT4LITERAL is used for integer and Boolean constants in the ASM representation of GLSL compiled shaders. Reactor can turn sNaN values into qNan when constructing Float constants, and thus integers bitcast from a float which were initialized from a reinterpreted integer may not preserve its original bit pattern. Instead construct the Float register values from Reactor Ints which are bitcast to Float. Bug: b/140302841 Change-Id: I4d915851c430dee4a752e06be0011c10d89fb79d Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/35888 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
- 11 Sep, 2019 4 commits
-
-
Nicolas Capens authored
Active development on dEQP has moved to the public Khronos repository. The version in AOSP is behind. Bug: b/137875321 Change-Id: I0bafba8f0325dc0e27af6c3ebc748fd6d7342350 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34969 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
Nicolas Capens authored
Function pointers returned through eglGetProcAddress should have a GL_APIENTRY calling convention to avoid mismatches with their declarations. Bug: b/140700303 Change-Id: I706ca788e54a897a66cfdf5ba959ec6e3dc718ee Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36228 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>
-
Ben Clayton authored
This is now the default in marl. Bug: b/140546382 Change-Id: Ic28537760b38c9ee051c8e527791495a57117466 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36190Tested-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Contains: 59068ee4c examples/fractal.cpp: Don't use rand() 7df53dd16 Add primes example ded37ceb8 Update README.md with build instructions b80c797df CMakeLists.txt: Don't default to building tests. d89fe34b6 CMakeLists.txt: Use explicit file lists 757566df0 Update README.md 8c98371e5 Presubmits: Enable warnings-as-errors. 0025389a1 CMakeLists: Add option to treat warnings as errors eeb070293 Fix all compiler warnings Commands: git subtree pull --prefix third_party/marl https://github.com/google/marl 59068ee4cf1f5ff5e691ff010c8d83b5f862c4fa --squash Bug: b/140546382 Change-Id: Ie37d6e1ce315aaeabeee5e006c5e1f6a7a5ca184
-
- 09 Sep, 2019 2 commits
-
-
Ben Clayton authored
59068ee4c examples/fractal.cpp: Don't use rand() 7df53dd16 Add primes example ded37ceb8 Update README.md with build instructions b80c797df CMakeLists.txt: Don't default to building tests. d89fe34b6 CMakeLists.txt: Use explicit file lists 757566df0 Update README.md 8c98371e5 Presubmits: Enable warnings-as-errors. 0025389a1 CMakeLists: Add option to treat warnings as errors eeb070293 Fix all compiler warnings git-subtree-dir: third_party/marl git-subtree-split: 59068ee4cf1f5ff5e691ff010c8d83b5f862c4fa
-
Jamie Madill authored
ANGLE uses this extension instead of the Xlib extension. Bug: angleproject:3876 Bug: b/140251624 Change-Id: I4bc420ddc340b8c35eca20d894718c8c3db68a3a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36148Reviewed-by:
Alexis Hétu <sugoi@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Jamie Madill <jmadill@chromium.org>
-
- 07 Sep, 2019 9 commits
-
-
Chris Forbes authored
In a few places we were always looking at component 0, which obviously doesn't go well. Bug: b/140648938 Test: dEQP-VK.*ldexp* Change-Id: I6a8698a56beab8ccc3b41a729d399b957cde9495 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36113Tested-by:
Chris Forbes <chrisforbes@google.com> Presubmit-Ready: Chris Forbes <chrisforbes@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Marl has its own repo and tests now, and so it is excessive to build and run these tests for downstream projects as well. Bug: b/140546382 Change-Id: Ic79db961a3bfae072a56ffeb7052165c127538d3 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36112Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
Bug: b/140546382 Change-Id: I106cde639419fb49d5d161555f1baa687bb12e91 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36111Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
This reverts commit 1359b66e. Reason for revert: still breaking chrome autorollers. Change-Id: I35d389f542beb3cfe31b1fa3143dfad4ab7e4a7a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36110Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
Bug: b/140546382 Change-Id: I7e25e913a1867ebbdee84b0575ddf67acb0b7cc6 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36109Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
This reverts commit df6cc08a. Reason for revert: Utterly breaks chrome autorollers Change-Id: I5bc05c538f30d689a078f47766c480be543d2a37 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36108Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
Bug: b/140546382 Change-Id: Ic104d5c3de500975316a96613b2101f37e11f11a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36031Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
Fixes squiggles on marl includes. Bug: b/140546382 Change-Id: If08700e453cade53d65926fc79eae09e6b19f05a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36069Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Will be upstreamed. Bug: b/140546382 Change-Id: Ifbbc14d5c5cd1cb6940642a1e6cc690c224e9bfe Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36068Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
- 06 Sep, 2019 3 commits
-
-
Ben Clayton authored
Having submodules inside subtrees breaks submodule update. Bug: b/140546382 Change-Id: I0e3e9591bfd1aa8813d1e8764f702d87c5ac5e84 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36030 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
* changes: Initial drop of Marl @ d3b8558c Squashed 'third_party/marl/' content from commit d3b8558ce
-
SwiftShader Regression Bot authored
Change-Id: Iac5636d2b9c947bfc14216be70ad8fe46a9a29c5 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36088 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
- 05 Sep, 2019 3 commits
-
-
Jamie Madill authored
../../third_party/SwiftShader/src\Yarn/Pool.hpp(254): note: see reference to function template instantiation 'std::shared_ptr<yarn::BoundedPool<sw::DrawCall::BatchData,16,yarn::PoolPolicy::Preserve>::Storage> std::make_shared<yarn::BoundedPool<sw::DrawCall::BatchData,16,yarn::PoolPolicy::Preserve>::Storage,>(void)' being compiled C:\dev\depot_tools\win_toolchain\vs_files\418b3076791776573a815eb298c8aa590307af63\win_sdk\bin\..\..\VC\Tools\MSVC\14.16.27023\include\memory(1866): warning C4316: 'std::_Ref_count_obj<_Ty>': object allocated on the heap may not be aligned 16 with [ _Ty=yarn::BoundedPool<sw::DrawCall::BatchData,16,yarn::PoolPolicy::Preserve>::Storage ] ../../third_party/SwiftShader/src/Vulkan/VkQueue.cpp(122): warning C4316: 'sw::Renderer': object allocated on the heap may not be aligned 16 Bug: angleproject:3876 Bug: b/140251624 Bug: b/140575360 Change-Id: I3016b8ba4e6557c9b7f1c27a387f03ff307e17de Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36048Reviewed-by:Alexis Hétu <sugoi@google.com> Tested-by:
Jamie Madill <jmadill@chromium.org>
-
Jamie Madill authored
This fixes the GN header check with Yarn. Enables further ANGLE integration. Also fixes a number of MSVC build errors and changes the output name of the Vulkan ICD on Windows to "vk_swiftshader" so that it matches the .def file used in CMake. Bug: angleproject:3876 Bug: b/140251624 Change-Id: Ie23ba965a2ee7f8b678499db22d6614f0a6666fa Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36009Reviewed-by:
Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Jamie Madill <jmadill@chromium.org>
-
Ben Clayton authored
Commands: git subtree add --prefix third_party/marl https://github.com/google/marl d3b8558ce8d2cf2cad1009a99aa3ff453b048639 --squash To update: git subtree pull --prefix third_party/SPIRV-Tools https://github.com/KhronosGroup/SPIRV-Tools <sha> --squash Bug: b/140546382 Change-Id: If3471eb3897b128613c874a9260e0ac390d27cf1
-