- 02 Jul, 2021 1 commit
-
-
James Rumble authored
Bug: b/192284721 Change-Id: I9b90cc5f77f7481c0bdcddb417679cf129ecc4c8 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55348Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Commit-Queue: Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
- 01 Jul, 2021 2 commits
-
-
Nicolas Capens authored
The initialization of static thread-local data is not observed by MemorySanitizer when inside a shared library, leading to false-positive use-of-uninitialized-data errors: https://github.com/google/sanitizers/issues/1409 We work around this by assigning an initial value to it ourselves on first use. Note that since the flag to check whether this initialization has already been done is itself a static thread-local, we must suppress the MemorySanitizer check with a function attribute. Bug: b/191050320 Change-Id: I356a89f90ff099e08a12f5562e0545ed14d93ee3 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55328Tested-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Corentin Wallez <cwallez@google.com>
-
Corentin Wallez authored
- maxComputeWorkGroupInvocations updated to 256. - maxComputeWorkGroupSize updated to 256, 256, 64. Bug: dawn:796 Change-Id: I00a9f4379bbc5b7c731b7c2c6f73bdc05baee3cf Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55249Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Commit-Queue: Corentin Wallez <cwallez@google.com> Tested-by:
Corentin Wallez <cwallez@google.com>
-
- 30 Jun, 2021 1 commit
-
-
Nicolas Capens authored
Android has no more known uses of SwiftShader's legacy OpenGL ES implementation. It has been replaced by SwANGLE, the combination of ANGLE and SwiftShader's Vulkan implementation. This was tested by aosp/1748769, but this change is meant to be easily reverted either upstream or downstream in case of unforeseen issues. Bug: b/147516027 Change-Id: I69cd0605443abd4ace0d08febeb7a53a3032417a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55308Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Jason Macnak <natsu@google.com>
-
- 29 Jun, 2021 3 commits
-
-
Nicolas Capens authored
Bug: build missing Reactor/Pragma.cpp Change-Id: I585d2e335cc70636ac6f7df8e7f6e788c1325497 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55288Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Jason Macnak <natsu@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Nicolas Capens authored
Enabling MemorySanitizer instrumentation for all Reactor routines can have too big of a performance impact. To support selective instrumentation, Pragma(MemorySanitizerInstrumentation, true) can be called to enable it for the next routine that gets created. It must be called before the Function<> constructor. Pragma state is thread local, so Pragma(MemorySanitizerInstrumentation, false) must be called after the routine has been created, to disable it again if instrumentation is not desired for subsequent routines created in this thread. Note that REACTOR_ENABLE_MEMORY_SANITIZER_INSTRUMENTATION=true enables MemorySanitizer instrumentation for Reactor routines even if the pragma state is false. Bug: b/191050320 Change-Id: Ie71aadeae140e85bda31554788288e138df0d08c Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54988 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
Corentin Wallez authored
- maxImageDimension3D updated to 2048. - maxFragmentCombinedOutputResources updated to 28. This is maxColorAttachments + maxPerStageDescriptorStorageBuffers + maxPerStageDescriptorStorageImages. 8 + 16 + 4 = 28. WebGPU doesn't have a limit for combined fragment outputs and requires at least this many. Bug: dawn:796 Change-Id: Ibda29f98d9fa6685ba8eac4b68dc03b70ae5100d Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55248 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Commit-Queue: Corentin Wallez <cwallez@google.com>
-
- 28 Jun, 2021 6 commits
-
-
Ben Clayton authored
Bug: swiftshader:161 Change-Id: Ib26cb1f6edb2549fc42420e7cc1579ce4ae36952 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55148 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Commit-Queue: Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Nicolas Capens authored
Previously the REACTOR_ENABLE_MEMORY_SANITIZER_INSTRUMENTATION macro definition controlled whether we compiled the code for properly instrumenting Reactor routines with the MemorySanitizer LLVM pass, or compile the code to unpoison all memory writes. This change makes us compile the code for both options, and select between the two at run-time. Currently this has no net effect, but it will allow selectively enabling MSan instrumentation to be done even when REACTOR_ENABLE_MEMORY_SANITIZER_INSTRUMENTATION is not defined (or false). Thus the define now means enabling instrumentation to always be performed. This way we'll be able to gradually enable more use of MSan instrumentation, where not already enforced by the build define. The ReactorUnitTests.Uninitialized test was changed to only run on build that have REACTOR_ENABLE_MEMORY_SANITIZER_INSTRUMENTATION set, since it already assumed MSan builds to always have instrumentation enabled. Bug: b/188205704 Change-Id: I54056ddc9b1d55fabbde6ae0f02d6c8cea3afad6 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54888 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Commit-Queue: Nicolas Capens <nicolascapens@google.com>
-
Stephan Hartmann authored
https://crbug.com/1122889 removed all defines for EGLAPI and GL_APICALL when compiled with GCC. However, that made all symbols of libEGL.so and libGLESv2.so hidden. Therefore SwiftShader can't be used with Chromium anymore. Bug: chromium:1122889 Change-Id: Ic05e7b5539537731141d945cf7944d07f4c389df Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55048 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Commit-Queue: Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
Nicolas Capens authored
The -warn-stack-size command line option won't be deprecated until the LLVM 13 release. This change also produces a compile-time error when LLVM 13+ is used so we won't fail to notice that the the stack size checking functionality has to be implemented using the per-function "warn-stack-size" attribute introduced by https://reviews.llvm.org/D104342. Note that development builds of LLVM use LLVM_MAJOR_VERSION=9999. Bug: b/191193823 Change-Id: I044d576a6dcd73354710783a7f7e042cb43254c5 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55188 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
Alexis Hetu authored
If an image has a single mip level, and filtering isn't LOD dependent, as is the case when using FILTER_MIN_POINT_MAG_LINEAR or FILTER_MIN_LINEAR_MAG_POINT, LOD computation is not necessary in order to perform image sampling and can be bypassed entirely. Bug: b/179889245 Change-Id: Ic69fe0c45211ccbb66c88c502c2dba1c50630aa7 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/52688 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> Commit-Queue: Alexis Hétu <sugoi@google.com>
-
SwiftShader Regression Bot authored
Reactor backend: LLVM Change-Id: Iccd8573f30562e5aaf0f5f56a389d6c1bf5da30e Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55068 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
- 25 Jun, 2021 3 commits
-
-
Peter Kasting authored
These match changes that have been previously landed in LLVM upstream. Bug: chromium:1223264 Change-Id: Ifb104adc7d513b38ad13d96171b290ff204a7de1 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55128 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Peter Kasting <pkasting@google.com> Commit-Queue: Peter Kasting <pkasting@google.com>
-
Nicolas Capens authored
Remaining occurences of this warning have been fixed. Note the warning is also added by -Wextra so we previously explicitly disabled it with -Wno-deprecated-copy. While removing the latter should suffice to re- enable it, it's useful to make it explicit since support for implicit copy constructors when a user-defined assignment operator has been defined may be removed in the near future. Bug: b/191417833 Change-Id: If6721ae900afd530750a7d05ccc40365924d4c25 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55028 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
Nicolas Capens authored
Reactor's Reference<> class represents a C++-like reference. It can be constructed from another reference, which creates a shallow copy, or it can be assigned another reference, which is a deep copy, but it cannot be assigned a new address. To enforce this, the address field was made constant. Also the default copy constructor outside the class definition, which is considered a user-provided copy constructor, was replaced with an in class defaulted default copy constructor. This makes it easier to understand that the copy constructor does default copying of the member fields when only looking at the class definition, takes fewer lines of code, and may enable some optimizations. Bug: b/191417833 Change-Id: Ied4ba3c7957b36efc06c19ce49f4e26309fb0c66 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55029 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
- 23 Jun, 2021 1 commit
-
-
Nicolas Capens authored
The Vulkan 1.2.182 spec mandates that "The UpdateAfterBind descriptor limits must each be greater than or equal to the corresponding non-UpdateAfterBind limit." Note that at the moment we do not advertise any of the update after bind features (e.g. descriptorBindingSampledImageUpdateAfterBind), but the Vulkan Validation Layers still expect these limits to be non-0. A descriptor pool creation flag and a descriptor binding flag which are disallowed when the features are not enabled prevent actual update after bind usage. Bug: swiftshader:160 Change-Id: Icce2ba987cb67a87544a406df144dfce8026b3f6 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55108Tested-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
- 21 Jun, 2021 1 commit
-
-
SwiftShader Regression Bot authored
Reactor backend: Subzero Change-Id: I7da14621e8aaf5e6730e2a2b884ad09984310e25 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54828 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
- 18 Jun, 2021 2 commits
-
-
Mikko Tiusanen authored
Changes VkTimeLineSemaphore::Shared::wait to pass on already signalled semaphores. Bug: b/188565298 Change-Id: I52089aca20d79392b1d9fb9ae2e0e04e8c91c6ff Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54908 Kokoro-Result: kokoro <noreply+kokoro@google.com> Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Sean Risser <srisser@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
Jari Komppa authored
Remove assert to accept OpAccessChain without indexes. Change-Id: Ie57f60d6ac35198e7d7a1b75071fcd985dc1da18 Bug: b/161516333 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54728Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
- 17 Jun, 2021 2 commits
-
-
Alexis Hetu authored
Legacy SwiftShader GL has a maximum framebuffer size of 8192 width and height. SwiftShader Vulkan's maximum framebuffer size was 4096, but this CL increases it to 8192. An issue was hit by using Chromium with SwANGLE on an iMac Pro 5k screen, where the 4096 limit was insufficient and causing a crash. The viewport max dimensions and bounds range had to be adjusted accordingly. According to the spec: "viewportBoundsRange[2] is the [minimum, maximum] range that the corners of a viewport must be contained in. This range must be at least [-2 × size, 2 × size - 1], where size = max(maxViewportDimensions[0], maxViewportDimensions[1])." Bug: chromium:1209250 Change-Id: I0ef15ccf2433aea348fd7946319ffb3406174873 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/55008Tested-by:
Alexis Hétu <sugoi@google.com> Commit-Queue: Alexis Hétu <sugoi@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Peter Kasting authored
Bug: chromium:1213098 Change-Id: Ief039d18b65eb338f42e60f78c864c52bc9becc1 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54928 Kokoro-Result: kokoro <noreply+kokoro@google.com> Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Peter Kasting <pkasting@google.com> Commit-Queue: Peter Kasting <pkasting@google.com>
-
- 16 Jun, 2021 1 commit
-
-
Nicolas Capens authored
This command line option is getting replaced with a module attribute in https://reviews.llvm.org/D103928. Temporarily disable it for LLVM versions newer than 11. Once LLVM 12 is released we should be able to use the attribute instead to retain this functionality. Note that upstream SwiftShader still uses LLVM 10, and the primary usage of this functionality is to prevent stack overflow in Chrome's fuzzers, which is not affected by this temporary change. Bug: b/191193823 Change-Id: I2edb0dc4df5d434540741bcb3007539311eb958a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54968 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Commit-Queue: Nicolas Capens <nicolascapens@google.com>
-
- 15 Jun, 2021 1 commit
-
-
Nicolas Capens authored
The account info of Gerrit Labels isn't fetched unless the DETAILED_ACCOUNTS parameter is added to the query: https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html This fixes the `canTest` result, setting it to true if either: - The author is a Googler (was previously working as intended) - The change has a Code-Review +1 or +2 from a Googler - The change has a Presubmit-Ready +1 from a Googler Change-Id: I5cd9881ad38a178fb5bbeb6e4aae4b5a18be9749 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54948Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com>
-
- 10 Jun, 2021 2 commits
-
-
Nicolas Capens authored
This reverts commit efe254de. b/189557997 was addressed by removing .gitmodules in the AutoRoller: https://skia-review.googlesource.com/c/buildbot/+/415736 Change-Id: Iec5ea73fce689f5286aedc486447ea0f498912b7 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54868Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Jason Macnak <natsu@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
Sean Risser authored
By using a C array instead of a std::vector, the data tables for BC6h are initialized without a constructor. This helps lower SwiftShader's startup costs. Tests: dEQP-VK.*bc6* Bug: b/174782098 Change-Id: I9bcfa2753bc6255ff16543d424cf8936c2817148 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54788Reviewed-by:
Alexis Hétu <sugoi@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Sean Risser <srisser@google.com> Commit-Queue: Nicolas Capens <nicolascapens@google.com>
-
- 08 Jun, 2021 1 commit
-
-
SwiftShader Regression Bot authored
Reactor backend: LLVM Change-Id: Ie03892e67b23995d84263e7b94c27204a67b8aab Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54808 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
- 07 Jun, 2021 1 commit
-
-
SwiftShader Regression Bot authored
Reactor backend: Subzero Change-Id: I30882faaf36d9291d9b487362fd088d2152a8b4e Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54708 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
- 03 Jun, 2021 3 commits
-
-
Nicolas Capens authored
This change adds a script which is to be called by the SwiftShader into Android AutoRoller: https://autoroll.skia.org/r/swiftshader-android It prepares a checkout for upload into the Android repo. Specifically, Android does not allow remote submodules, so this script removes them. Note SwiftShader does not require any submodules to build the library; they are optional for development purposes. Bug: b/189557997 Change-Id: I36b4ae59cd843f1c69146f0f52ce8f323c6bc15a Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54768Reviewed-by:
Alexis Hétu <sugoi@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
Nicolas Capens authored
The vk::GraphicsState constructor does not initialize all members in all code paths. We were relying on the zero-initializing done by vk::allocate() which is used to allocate vk::GraphicsPipeline which in turn contains a GraphicsState member. We want to change vk::allocate() to no longer zero-initialize all memory, to catch more MemorySanitizer errors made by applications. Thus we must also not rely on such automatic initialization ourselves. Note that this change might also hide MemorySantizer violations committed by the application side. For example some state is only copied from VkGraphicsPipelineCreateInfo into vk::GraphicsState on construction when flags indicate they're not dynamic state. If the application forgets to makerecord commands that set the dynamic state, their value is undefined: Vulkan 1.2.178 section 6. Command Buffers: "When a command buffer begins recording, all state in that command buffer is undefined." Vulkan 1.2.178 section 10.11. Dynamic State: "If the state is specified as dynamic in the new pipeline object, then that command buffer state is not disturbed. Before any draw or dispatch call with this pipeline there must have been at least one call to each of the corresponding dynamic state setting commands since the command buffer recording was begun, or the last bound pipeline object with that state specified as static, whichever was the latter." Thus once sw::allocate() no longer also zeroes this data, we should revert the value-initialization where possible and ensure we don't touch the uninitialized data ourselves, unless as a consequence of an application bug. Bug: b/140991626 Change-Id: I060e8d8a79e93b0676669eed361fab4f86ab1b56 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/53089 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>
-
Nicolas Capens authored
vk::allocate() zero-initializes its memory, which was nulling the VkSpecializationInfo::pMapEntries field in case the mapEntryCount is 0. We'll be changing vk::allocate() to not zero-initialize, to catch cases where applications might incorrectly be relying on it, with MemorySanitizer. So we have to also not be relying on it. Bug: b/140991626 Change-Id: I5917c902c0af27985556340dfc1dbae79010a125 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54468 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>
-
- 02 Jun, 2021 2 commits
-
-
Sean Risser authored
clang-format will modify non source files and has no configuration options to ignore bash, python, or extensionless files. This CL is a follow up for: https://swiftshader-review.googlesource.com/c/git-hooks/+/54569 Bug: b/187094215 Change-Id: I72953bd07e3c16b70aab441a25c27abae31b6a87 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54689 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Commit-Queue: Sean Risser <srisser@google.com> Tested-by:
Sean Risser <srisser@google.com>
-
Sean Risser authored
The Vulkan spec is being clarified to explain that the FragCoord passed to a shader should use the unclamped depth value and that only the depth test and depth write should use clamped values. Bug: b/184063472 Change-Id: Ic76c13512745abea2181475eff5147134a1bf147 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54668 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Sean Risser <srisser@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Commit-Queue: Sean Risser <srisser@google.com>
-
- 31 May, 2021 1 commit
-
-
Nicolas Capens authored
This update advances dEQP to a revision where the 1.2.6 branch is merged into the master branch. It uses the new 'chunked' testlists. Notable new tests: - Add tests for VK_EXT_provoking_vertex (https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/2092) - Require geometry shaders for adjacency topologies (https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/2906) - Add early fragment tests (https://gitlab.khronos.org/Tracker/vk-gl-cts/-/issues/2738) Tests: dEQP-VK.* Bug: b/140302392 Bug: b/189588731 Bug: b/167582422 Fixes: b/189334760 Fixes: b/185814882 Change-Id: I278224b3e709c714f1e7e6fb750eeffbfba84578 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54568Tested-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Sean Risser <srisser@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
- 29 May, 2021 2 commits
-
-
SwiftShader Regression Bot authored
Reactor backend: LLVM Change-Id: Id3e18f2779facfe3f441f684a40540a86d904643 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54489Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
Nicolas Capens authored
Using -DDEQP_TARGET=x11_egl caused a build error on some systems: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/Scrt1.o: in function `_start': (.text+0x20): undefined reference to `main' Using 'default' instead makes the build succeed, and makes XCB WSI tests pass. However, GLES tests crash. Since we no longer need them due to SwANGLE, with SwiftShader becoming Vulkan-only, this change removes them from the test run. Also, the dEQP build is reduced to just the deqp-vk target. Lastly, code coverage generation on 'daily' test runs is disabled. It produced errors such as: Failed to process test coverage for test 'dEQP-VK.***'. llvm-profdata errored. Cause: exit status 1 It was already disabled locally on the Regres bot to avoid these errors. Bug: b/189469951 Bug: b/152192800 Change-Id: I07383e1168cc322bb9247ed39db091f91c054b6d Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54589 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
- 27 May, 2021 4 commits
-
-
Sean Risser authored
Bug: b/184063472 Change-Id: Ife9e8c7d90d43695b712ac6d1d44f9b4ec73a4df Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54669Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Sean Risser <srisser@google.com> Commit-Queue: Sean Risser <srisser@google.com>
-
Nicolas Capens authored
Worker::current is a static thread_local which gets intialized to null, which gets checked for in Scheduler::Fiber::current(). Unfortunately MemorySanitizer does not observe the initialization when Marl is used within a shared library, when the Linux dynamic loader is not instrumented and its TLS initialization is not otherwise intercepted and handled correctly. This change decorates Scheduler::Fiber::current() with __attribute__((no_sanitize_memory)) to suppress instrumenting it with use-of-uninitialized-data checks. Bug: chromium:1211047 Change-Id: I61b584922d9aba5d67991ce916c69102734f2b61 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54610Reviewed-by:
Alexis Hétu <sugoi@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com>
-
Sean Risser authored
git-hooks tracks git hook scripts for SwiftShader. Using git config we can tell git to use these scripts instead of what's in .git/hooks. Bug: b/187094215 Change-Id: I2df090c47ceeb1b352960576a34f259b75946302 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54528 Kokoro-Result: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Sean Risser <srisser@google.com> Commit-Queue: Sean Risser <srisser@google.com>
-
Nicolas Capens authored
Bug: b/189334760 Change-Id: I27d8e54d20a534ffd5f7b0deb8d0c55c05baabdc Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/54588 Kokoro-Result: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-