- 19 Jul, 2019 1 commit
-
-
Nicolas Capens authored
The required or desired behavior on out-of-bounds accesses depends on the robustness feature, storage class, static analysis, debugging state and paranoia level preference. Specifically, this change: - Omits bounds checks on local variable initialization. - Omits bounds checks on modf() and frexp() output variables. - Bounds checks on image read/write instead of using robustBufferAccess feature setting. - Bounds checks on OpCopyMemory instead of using robustBufferAccess feature setting. Bug: b/131224163 Change-Id: I199e73d42d9cce0645792dd1d876ea69d4ec3835 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33988 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>
-
- 17 Jul, 2019 3 commits
-
-
Nicolas Capens authored
In https://swiftshader-review.googlesource.com/c/SwiftShader/+/33028 we modified the conversion of 8-bit color elements to 16-bit ones from duplicating the byte, to putting 0 in the lower byte, and adjusting the normalization factor from 0xFFFF to 0xFF00 accordingly. However, the latter wasn't being done for B8G8R8A8. Bug: chromium:979652 Bug: swiftshader:122 Change-Id: I621a600128e1b028b3303917acd826a7bf4630dd Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34228 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Alexis Hetu authored
This cl implements the VK_MVK_macos_surface extension, which adds the vkCreateMacOSSurfaceMVK function on MacOS. According to the spec: "The VK_MVK_macos_surface extension is an instance extension. It provides a mechanism to create a VkSurfaceKHR object (defined by the VK_KHR_surface extension) that refers to an NSView, the native surface type of macOS, which is underpinned by a CAMetalLayer, to support rendering to the surface using Apple’s Metal framework." Bug b/137673628 Change-Id: Iacf7696b1d9e52d7349ea4efa01f0acdd09a6c8f Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33848Reviewed-by:
Hernan Liatis <hliatis@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Not passing does not equal failing, and not failing does not equal passing, as there's the muddy waters of UNSUPPORTED and friends. Check for transitions of [not failing -> failing] and [not passing -> passing] as reasons to say something. Bug: b/137671242 Change-Id: Ibb612531da494738c411a1b3f1ac40a5c5078fdc Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34188 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
- 16 Jul, 2019 3 commits
-
-
Alexis Hetu authored
The assert was firing off when there were already MAX_DESCRIPTOR_SET_COMBINED_BUFFERS_DYNAMIC dynamic descriptors (which is valid), while the last set layouts contained no dynamic descriptors, because the offset was already set to MAX_DESCRIPTOR_SET_COMBINED_BUFFERS_DYNAMIC, which shouldn't matter if there are no dynamic descriptors left. Bug b/118386749 b/123244275 Change-Id: I1536e6a47b7837c6b052d4e169a5396daf7d34cb Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34148Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Alexis Hetu authored
- The SamplingRoutine cache is now owned by the Device and has the same lifetime as the device, which means it gets released when the device gets released. - Added a utility class, SamplingRoutineCache, to contain the cache and release all routine entries upon destruction. - Added a pointer to the current device in the sampler object in order to retrieve it during sampling, in order to access the routine cache - The cache is now internally an LRUCache, so it can't cache a large quantity of routines and take up a lot of memory. Bug b/129523279 b/137649247 b/137524292 chromium:971325 Change-Id: If4ff1fbc87962355d0a281b9d0acace4316a02b8 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/32688Tested-by:
Alexis Hétu <sugoi@google.com> Presubmit-Ready: Alexis Hétu <sugoi@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
We previously created and held a TargetMachine per JITRoutine as the routine could be created with different optimization levels, which is a property used to create the TargetMachine. However, a llvm::TargetMachine instance can consume a lot of memory and JITRoutines can accumulate in caches, causing dEQP test batches of 1000 to fail as all the system memory is exhausted on low-memory devices. Optimization level is the only varying property of each TargetMachine, so simply cache these by optimization level on the JITGlobals. Until we start using compiling with different optimization levels, this will ensure a single TargetMachine is shared across all JITRoutines. Bug: b/137524292 Change-Id: I97298708ea4ed14a81aa8026a51926f571d37148 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34128 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
- 15 Jul, 2019 6 commits
-
-
Alexis Hetu authored
Make sure all allocations within the pool are 16 bytes aligned Bug b/137554711 Change-Id: I7e9531b720ae07390e0089768f92fd95c62d6afb Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33250Tested-by:
Alexis Hétu <sugoi@google.com> Presubmit-Ready: Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Sean Risser authored
This is to prevent undefined behavior if the calculation overflows. Moving the calculation won't cause issues with the clipping since the projected coordinates are not used in the clipping calculations. Bug chromium:979644 Change-Id: I5a6fba0f067d8d3ad310de573bacd2f68dfe4b78 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34109 Presubmit-Ready: Sean Risser <srisser@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com> Tested-by:
Sean Risser <srisser@google.com>
-
Alexis Hetu authored
Fixed typos where end() was used instead of begin() Bug b/137554711 Change-Id: I5faff14d400a644146501a941c35d503535355c4 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34111Tested-by:
Alexis Hétu <sugoi@google.com> Presubmit-Ready: Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
Coroutines have a larger performance overhead to regular functions. If a rr::Coroutine does not call Yield(), then keep it as a regular function, and stub `coroutine_await` and `coroutine_destroy`. Bug: b/135609394 Bug: b/137167505 Change-Id: Id890e86eb3602f9cd9ed4e68e50c68a98705c753 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33950Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
This pass is automatically added by LLVM when using the CoroSplit pass which is not peformed by regular functions. These passes have been shown to provide a big performance gain for certain dEQP tests. Bug: b/135609394 Bug: b/137167505 Change-Id: Iecdae495bc741c855c38daf67f95ad83155fc213 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33969 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Jeff Muizelaar authored
Using =A is not the right constraint for x86-64. rdtsc is actually used as an example in the gcc documentation and for x86-64 something like "=a"(tickl),"=d"(tickh) should be used. Instead of worrying about this we can just use the builtin. Change-Id: Ied720de0861ff9231a4a4cdf85b75945fe478056 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34108 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Jeff Muizelaar <jmuizelaar@mozilla.com>
-
- 11 Jul, 2019 2 commits
-
-
Nicolas Capens authored
The regular C++ operator new calls the installed new-handler on out-of-memory, which by default throws std::bad_alloc when exception handling is enabled, or aborts when not. Under no circumstance is null returned. Furthermore, LLVM installs a new-handler itself, which also ends up aborting the program. Using the std::nothrow version of new does not work because it still calls the new-handler. Installing our own non-fatal new-handler is also futile because the new operator will re-attempt allocation. Setting the new-handler to nullptr will cause the nothrow version of new to return null on out-of-memory. However, this still overrides any new handler which the application may have installed, or, can be overridden by the application again at any point. Instead just use legacy malloc(), which is guaranteed to never throw and returns null on failure. This is already checked for by vk::Create() and it reports VK_ERROR_OUT_OF_HOST_MEMORY. Bug: b/137093675 Change-Id: I6c9ccf738cfd21af9e52382d6e7755071d613d39 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34028 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Alexis Hetu authored
Using a non SRGB format with VK_COLOR_SPACE_SRGB_NONLINEAR_KHR yields a resulting image in the wrong color space. Making sure a surface format where format and color space are both SRGB fixes the issue. Bug b/137088174 Change-Id: I934e6b60afe5f65d22832162e48aecef773627e8 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34048Tested-by:
Alexis Hétu <sugoi@google.com> Presubmit-Ready: Alexis Hétu <sugoi@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
- 10 Jul, 2019 3 commits
-
-
Ben Clayton authored
Documentation: http://llvm.org/doxygen/structllvm_1_1EarlyCSEPass.html Bug: b/135609394 Change-Id: Ie7c6a99be46832797c3871b00fee33dea979f207 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33951 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
Remove all the explicit config passing to each of the functions. Bug: b/137167988 Change-Id: Ie8ea956d2365f1901d75b0d10c9e649485d78bf4 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33769Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
rr::Config holds the full reactor configuration state. rr::Config::Edit holds edits on a config, which can be applied on top of the current defaults. Default configurations are updated atomically, preventing modifications to the default state from tearing. Bug: b/137167988 Change-Id: Ib05f2cfc31ab22fb9a891a267fffe33c18691028 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33768 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
- 08 Jul, 2019 1 commit
-
-
Chris Forbes authored
This will halve the size of the input and output arrays used to communicate with the shader. This is likely to have been already cleaned up by llvm, but better to not make the mess to start with. Bug: b/125909515 Change-Id: I960647f808b722fe8ad38ff716df1461e1eae4ef Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33788Tested-by:
Chris Forbes <chrisforbes@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
- 05 Jul, 2019 6 commits
-
-
SwiftShader Regression Bot authored
Change-Id: I8c7b60b08c983802b659910180ec093c8e605c21 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33808 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
No other fields in this class are prefixed with 'current' and it's in a class named State, so rename to make consistent. Bug: b/126126820 Change-Id: I8eb26546141d1c11beb9acf57883d3d0835847b2 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33354Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
getType(), getObject() and getFunction() are only internally used, make them private. Minor refactoring related to spirv function inlining. Bug: b/133213304 Change-Id: I75f9f5488a8485161d534b56eb6530c2946bf49e Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33353Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Function holds all the blocks used by the function. Moved various function-specific methods from SpirvShader to this new Function inner class. This change is currently a pure-refactor (no change in behavior), but is required for function inlining in SpirvShader. Bug: b/133213304 Change-Id: I50c7ecca8ce518d8df054c2461410c0acd4e1f52 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33352 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
These are only used during SpirvShader::emit(), and will require separate namespacing when functions are inlined. Bug: b/133213304 Change-Id: I8cf6cd76af35984f0f24109665a991492158bf16 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33351 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
GenericValue is only used by SpirvShader so move it as a private inner class of SpirvShader. Part of the foundations of much larger refactoring required for function inlining in SpirvShader. Bug: b/133213304 Change-Id: I75484c3d036b82f3bc6a735034a7c1b04f05f600 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33350Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
- 04 Jul, 2019 14 commits
-
-
Nicolas Capens authored
Bug chromium:980816 Change-Id: Ic4393668f82316e475baa5e753d891dfb1e30572 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33728 Presubmit-Ready: Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Alexis Hétu <sugoi@google.com>
-
Ben Clayton authored
May unlock features that are not exposed by march. Change-Id: I4f10dfc93f75eab502824ec155daa9fbbb3d3d55 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33773Tested-by:
Nicolas Capens <nicolascapens@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Experiments show substantial performance gains. Bug: b/135609394 Change-Id: I62a6b9dd292cafe92aa5558a84c460594b51197c Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33772Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Alexis Hetu authored
Fixed R8G8_SRGB and R8G8B8_SRGB in the Blitter. Enabled R8G8_SRGB tests to make sure the fix is correct. Change-Id: Ibe7addd3f635f353abb09e0391a9a30d20392fbf Tests: dEQP-VK.*r8g8_srgb* Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33530 Presubmit-Ready: Alexis Hétu <sugoi@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Alexis Hétu <sugoi@google.com>
-
Ben Clayton authored
Let's just initialize these to zero, and let the optimizer remove redundant assignments. Bug: b/136149446 Change-Id: Ia776bae4433f78f5a66b16f275e728a70dd4e18d Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33468Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Chris Forbes <chrisforbes@google.com>
-
Ben Clayton authored
If robustness is disabled, don't bother zeroing disabled lanes. Gives the LLVM optimizer & backend some more wiggle room. Bug: b/135609394 Change-Id: I425eba2b48601a35dc40aa8ca071e6e61f35024f Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33708 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
Bug: b/135609394 Change-Id: Ic566f2ef6d66e31b434d29b23aafd954a05958a4 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33709Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
Replace the old 'runOptimizations' flag on Nucleus::acquireRoutine() and Nucleus::acquireCoroutine() with a new OptimizationLevel enumerator. runOptimizations was always true, and there is already the rr::optimization extern to control the optimization passes performed. All Function and Coroutines are now passed the new vk::ReactorOptimizationLevel. This will be changed to a non-Default value in another CL. Bug: b/135609394 Change-Id: I1154da05d413b18a471a3818fbb03f356a3d0e6c Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33482Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Split the scattered LLVM global variables into 3 new classes: • JITGlobals is a singleton that holds all the immutable machine specific information for the host device. • JITBuilder holds all the LLVM state for building routines. • JITRoutine is a rr::Routine that holds a LLVM JIT session, compiler and object layer as each routine may require different target machine settings and no Reactor routine directly links against another. This reduce all the global varibles to down to one - 'jit' a JITBuilder. In theory, this can be marked as TLS to remove the global reactor mutex lock. These change also make it possible to specify per-function JIT optimization settings (implemented in a follow-up change). Change-Id: If4c90de444830f398eb79081fd349f313a8d3bd7 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33481Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-
Ben Clayton authored
dEQP-VK.synchronization.internally_synchronized_objects.pipeline_cache_compute When the wind is blowing in the right direction, this test can exceed the per-test 2GB sandbox memory limit, causing a flaky out-of-memory crash. Bug: b/133127573 Change-Id: Ie403d91738c05258639be077aa31ec36d92d109e Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33688Tested-by:
Ben Clayton <bclayton@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Change-Id: I3833a203ae7635845ea3b8ceb5e323565a92be18 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33487 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
Bug: b/132353920 Change-Id: Ic7950ea29be6fd0dc7712813c10cdd2dfab73b90 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33548Reviewed-by:
Chris Forbes <chrisforbes@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
-
Ben Clayton authored
Change-Id: Ieaec8e9dd2017803d862ce8bcdc6b00582b7d45b Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33486 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
Ben Clayton authored
Change-Id: I6247e0b5eef4639527ea15e7c5af115e5954a342 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33485 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com> Tested-by:
Ben Clayton <bclayton@google.com>
-
- 03 Jul, 2019 1 commit
-
-
Alexis Hetu authored
- Removed twoSidedStencil, which was always true when stencil is enabled - Removed unused enums and functions - Removed custom new/delete operators - Used VkFrontFace type for frontFace Bug b/132280877 Change-Id: I440d5e910e50de0ac8049d3a56848fa8d2de3493 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/33531 Kokoro-Presubmit: kokoro <noreply+kokoro@google.com> Tested-by:
Alexis Hétu <sugoi@google.com> Reviewed-by:
Nicolas Capens <nicolascapens@google.com>
-