xinglong.zhu [Fri, 4 Jan 2019 08:55:20 +0000 (16:55 +0800)]
gles31:es31fSSBOLayoutTests limit m_maxBlocks and m_maxBlockMembers for low ram device
Memory requirement for cts CtsDeqpTestCases
dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer#5
reduced from 230MB to 36MB
Issue:
121364689
Test: run cts -m CtsDeqpTestCases -t dEQP-GLES31.functional.ssbo.layout.random.all_shared_buffer#5
Change-Id: I2a66263f041265e8697e4b270132b9889486ce4f
(cherry picked from commit
237916d03377a469e30dd36087738b069f83a19a)
Chris Forbes [Thu, 21 Mar 2019 20:59:49 +0000 (13:59 -0700)]
Merge remote-tracking branch 'khronos/master' into deqp-dev
Change-Id: Id1dbec36bea53236bcb7f4fc997a3e2b7b9c832a
Jordan Justen [Tue, 12 Mar 2019 07:17:53 +0000 (00:17 -0700)]
Make renderdoc_app.h optional at build time
Since renderdoc support is optional at runtime, this change makes it
also optional at build time. If the renderdoc_app.h file doesn't exist
at the expected location, then a no-op stub version of the
RenderDocUtil class is built instead.
Components: Vulkan, Framework
Change-Id: Iedc4bcddf47ac5f471911ad6d8e37439cd9e0d90
Alexander Galazin [Wed, 20 Mar 2019 16:10:35 +0000 (12:10 -0400)]
Revert "Make renderdoc_app.h optional at build time"
This reverts commit
1225d4ab8375e88b39f73bc946a7afcb51aa8156.
Change-Id: I3c2f71b3bc54adb221f1357f7a4b31e719dc3a20
Jari Komppa [Wed, 6 Mar 2019 08:41:25 +0000 (10:41 +0200)]
Improve shader cache hashing
This change adds FNV-1 hash algorithm and a check whether a shader is
already in the cache before writing it there. In multi-threaded shader
compilation the cache might have written multiple copies of the same
shader into the cache, wasting disk space.
Affects:
None
Components: Vulkan
VK-GL-CTS issue: 1641
Change-Id: Ideaed34f49994f5da50b75066e611e60023eccb1
Jordan Justen [Tue, 12 Mar 2019 07:17:53 +0000 (00:17 -0700)]
Make renderdoc_app.h optional at build time
Since renderdoc support is optional at runtime, this change makes it
also optional at build time. If the renderdoc_app.h file doesn't exist
at the expected location, then a no-op stub version of the
RenderDocUtil class is built instead.
Components: Vulkan, Framework
Change-Id: Ic4b43500b4ead50c4728d2ff3bf098d44e00a9a6
Tapani Pälli [Fri, 1 Mar 2019 11:07:35 +0000 (13:07 +0200)]
framework: propagate ResourceError exception from postIterate
Change throws ResourceError exception in TestCaseWrapper::iterate in
case postIterate threw one.
Change-Id: I9a3fed58f21dd6f594488fc998ae5bd685a733ec
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
Daniel Koch [Wed, 13 Mar 2019 19:15:48 +0000 (15:15 -0400)]
Move spirv/glslang utils to common module
VK-GL-CTS Issue: 1651
Component: OpenGL
Affects: KHR-GL*.gl_spirv.*
Change-Id: I1fdc617523ac467458952e9ec2df67abf80657c3
David Neto [Tue, 19 Mar 2019 18:56:29 +0000 (14:56 -0400)]
Amber: Initialize the delegate to NULL
The delegate can be used to log calls and time them.
For now, we don't want any such logging. But we do have
to initialize the delegate rather than use an uninitialized
pointer.
Change-Id: I1379b9810f3acd67d4d7116d407eb4e0c6ee7bb3
Alexander Galazin [Tue, 19 Mar 2019 15:04:23 +0000 (16:04 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.3 into vk-gl-cts/master
Change-Id: I0d8d57b196da13538a026a3abea3ebd6b6ed0cde
Alexander Galazin [Tue, 19 Mar 2019 14:26:12 +0000 (15:26 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: Iacfb659e3cb7bcb1d144f843a9011472c18c63fe
David Neto [Mon, 18 Mar 2019 21:56:06 +0000 (17:56 -0400)]
Update Amber so it detects Vulkan on Android
Components: Vulkan
Change-Id: I0a584c5617c723dc763933fd8e20fe621ac46970
Jeff Bolz [Wed, 27 Feb 2019 16:22:32 +0000 (10:22 -0600)]
Add tests for VK_NV_cooperative_matrix
Components: Vulkan
New tests: dEQP-VK.compute.cooperative_matrix.*
Change-Id: I1f78c068510466793ba7407347c2b91b30ee4831
Jari Komppa [Thu, 7 Feb 2019 08:10:16 +0000 (10:10 +0200)]
Add test for concurrent compute
Added test that runs identical payload on two queues with different
priority levels, and checking that the lower priority queue does not
finish first, adding a note to the log if the priorities seem to be
reversed. At the end it is also verified that both queues did the
work.
New test:
dEQP-VK.compute.basic.concurrent_compute
Components: Vulkan
VK-GL-CTS issue: 1509
Change-Id: Ib5d52dcbb3cee0e07c4d14bbb8d61d2f1ee2a8c5
Lingfeng Yang [Fri, 1 Mar 2019 07:58:41 +0000 (23:58 -0800)]
Send external api base extensions when not core
If the base extension for external semaphore/fence/memory
is not core (i.e., in Vulkan 1.0), external API tests
will send an insufficient set of device extensions to
the Vulkan driver.
Also, add required extensions (if not core) for
VK_ANDROID_external_memory_android_hardware_buffer.
VK-GL-CTS Issue: 1632
Affects:
dEQP-VK.api.external.*
Components: Vulkan
Change-Id: I666f87ef25260d4f3fe6d1d9a6ff8a522f2322b3
Alexander Galazin [Fri, 15 Mar 2019 09:31:51 +0000 (10:31 +0100)]
Merge vk-gl-cts/opengl-cts-4.6.0 into vk-gl-cts/master
Change-Id: I9ae207c6ce78844662c23df5016a584742466b63
Andres Gomez [Wed, 27 Feb 2019 13:03:56 +0000 (15:03 +0200)]
GL_ARB_enhanced_layouts: use separable programs
Currently we are testing bogus inputs without a matching counterpart
in the output interface of the previous shader. This is needed since,
otherwise, having a matching output would mean that we would have to
introduce the same error we are trying to test in the input interface
and that could lead to a misleading linking error.
However, not having an output counterpart can also lead to a
misleading linking error.
In other tests we have avoided this by not making a static use of the
tested input. However, when checking for the limit on the number of
input locations that can be used in a specific interface, this
strategy cannot be used since non statically used variable do not
count against this limit.
From page 48 (page 52 of the PDF) of the GLSL 4.60 v.5 spec:
" There is an implementation-dependent limit on the number of
locations that can be used, and if this is exceeded it will cause
a link-time error. (Declared input variables that are not
statically used do not count against this limit.)"
Therefore, the strategy used for this test is to build individual
separable programs for each stage.
From the ARB_separate_shader_objects spec v.25:
" With separable program objects, interfaces between shader stages
may involve the outputs from one program object and the inputs
from a second program object. For such interfaces, it is not
possible to detect mismatches at link time, because the programs
are linked separately. When each such program is linked, all
inputs or outputs interfacing with another program stage are
treated as active. The linker will generate an executable that
assumes the presence of a compatible program on the other side of
the interface. If a mismatch between programs occurs, no GL error
will be generated, but some or all of the inputs on the interface
will be undefined."
Components: OpenGL
VK-GL-CTS issue: 1628
Affects:
KHR-GL44.enhanced_layouts.varying_location_limit
Change-Id: If120f3f2d397be0b53c60033768db60eb6fed968
Andres Gomez [Thu, 3 Jan 2019 12:17:18 +0000 (14:17 +0200)]
GL_ARB_enhanced_layouts: no structs as VS inputs
From page 48 (page 52 of the PDF) of the GLSL 4.60 v.5 spec:
" It is a compile-time error to declare a vertex shader input with,
or that contains, any of the following types:
* A boolean type
* An opaque type
* A structure"
Components: OpenGL
VK-GL-CTS issue: 1614
Affects:
KHR-GL44.enhanced_layouts.varying_structure_member_location
Change-Id: Ied52fd09639de179db480b6a627b65208a54250a
Andres Gomez [Wed, 23 Jan 2019 16:28:59 +0000 (18:28 +0200)]
GL_ARB_enhanced_layouts: remove dead code
Additionally, make us of the new debugging macro to ease checking that
we are testing just the correct and only cause for a failure report.
Components: OpenGL
VK-GL-CTS issue: 1617
Affects:
KHR-GL44.enhanced_layouts.xfb_duplicated_stride
Change-Id: I2bb03db22743ae12d17c3da1654d082236d2e2e6
Andres Gomez [Wed, 9 Jan 2019 15:38:12 +0000 (17:38 +0200)]
GL_ARB_enhanced_layouts: fix interstage interfaces
Multiple test were reporting misleading fails due to out-in interface
mismatching.
Additionally, removed dead code paths.
Finally, make us of the new debugging macro to ease checking that we
are testing just the correct and only cause for a failure report.
Components: OpenGL
VK-GL-CTS issue: 1608
Affects:
KHR-GL44.enhanced_layouts.xfb_block_member_buffer
KHR-GL44.enhanced_layouts.xfb_capture_unsized_array
KHR-GL44.enhanced_layouts.xfb_exceed_buffer_limit
KHR-GL44.enhanced_layouts.xfb_exceed_offset_limit
KHR-GL44.enhanced_layouts.xfb_invalid_offset_alignment
KHR-GL44.enhanced_layouts.xfb_multiple_vertex_streams
KHR-GL44.enhanced_layouts.xfb_output_overlapping
KHR-GL44.enhanced_layouts.xfb_too_small_stride
Change-Id: I0fb8f851b7cbec4c8cb4ee9fbad544c32e130a99
Andres Gomez [Wed, 23 Jan 2019 15:56:33 +0000 (17:56 +0200)]
GL_ARB_enhanced_layouts: fix interstage interfaces
This test was reporting a misleading fail due to out-in interface
mismatching.
Additionally, in the past another "fail" status was "corrected" by
excluding all non-positive cases making it, actually, not a negative
test. Now, while fixing the problems in the interface matching, we
re-introduce the negative cases back.
Also, removed dead code paths.
Finally, make us of the new debugging macro to ease checking that
we are testing just the correct and only cause for a failure report.
Components: OpenGL
VK-GL-CTS issue: 1607
Affects:
KHR-GL44.enhanced_layouts.xfb_variable_stride
Change-Id: If6564a9feb9831d101b0d5073ec3d241a4a8ac81
Andres Gomez [Mon, 7 Jan 2019 23:18:40 +0000 (01:18 +0200)]
GL_ARB_enhanced_layouts: use centroid and sample
When checking for aliasing using mixed auxiliary storages, the tests
checking the usage of centroid and sample were only for the fragment
shader inputs. These qualifiers, although ignored, can also be used in
the rest of the stages.
Components: OpenGL
VK-GL-CTS issue: 1613
Affects:
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_auxiliary_storage
Change-Id: I4ec1609a63a225ccd8c2ed7b82eb5477a04b6cba
Andres Gomez [Mon, 7 Jan 2019 23:00:49 +0000 (01:00 +0200)]
GL_ARB_enhanced_layouts: mind double types
The special conditions when using the component qualifier with doubles
were not taken into account.
Additionally, the test was reporting a misleading fail due to
non-coherent usage of the "flat" interpolation qualifier. This is now
fixed.
Finally, the generator has been simplified using the refactored code.
Components: OpenGL
VK-GL-CTS issue: 1611
Affects:
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_auxiliary_storage
Change-Id: I4380ba720f4ea2b2326484d6c8b3e8fc58b1b5e5
Andres Gomez [Mon, 18 Feb 2019 14:49:28 +0000 (16:49 +0200)]
GL_ARB_enhanced_layouts: mind double types
The special conditions when using the component qualifier with doubles
were not taken into account.
Additionally, the generator has been simplified using the refactored
code.
Components: OpenGL
VK-GL-CTS issue: 1616
Affects:
KHR-GL44.enhanced_layouts.input_component_aliasing
KHR-GL44.enhanced_layouts.output_component_aliasing
KHR-GL44.enhanced_layouts.varying_component_of_invalid_type
KHR-GL44.enhanced_layouts.varying_component_without_location
KHR-GL44.enhanced_layouts.varying_exceeding_components
Change-Id: I33c9735a8ef02cf5257f6783cf7856911e4af9d8
Andres Gomez [Thu, 20 Dec 2018 15:29:13 +0000 (17:29 +0200)]
GL_ARB_enhanced_layouts: use component 0 for mat
When checking types that won't support the component qualifier, in the
case of matrixes, just use the universally accepted value in case the
keyword would be accepted: 0.
Otherwise, we won't be sure whether the test is passing because the
reported failure is the expected one: that matrix won't accept the
component qualifier.
Components: OpenGL
VK-GL-CTS issue: 1615
Affects:
KHR-GL44.enhanced_layouts.varying_component_of_invalid_type
Change-Id: I5e53ecdcb4e73f9ca528f3232bfa9405782db43e
Andres Gomez [Mon, 7 Jan 2019 17:46:16 +0000 (19:46 +0200)]
GL_ARB_enhanced_layouts: mind double types
The special conditions when using the component qualifier with doubles
were not taken into account.
The tests generator is now simplified using the refactored code.
Components: OpenGL
VK-GL-CTS issue: 1610
Affects:
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_interpolation
Change-Id: I44763cf9e9e3b11fe17519ab307b28cc5485706d
Andres Gomez [Fri, 4 Jan 2019 12:46:27 +0000 (14:46 +0200)]
GL_ARB_enhanced_layouts: mind aliasing bit width
Currently, when location aliasing was happening, we were only checking
if the underlying numerical type was the same to allow it.
From page 67 (page 71 of the PDF) of the GLSL 4.60 v.5 spec:
" Further, when location aliasing, the aliases sharing the location
must have the same underlying numerical type and bit
width (floating-point or integer, 32-bit versus 64-bit, etc.)"
Additionally, we were repeating two times the same tests. For example
we would check if, with float and int, they would be allowed if float
was in the component 1 and int in component 3 two times. The test
generation has been now simplified.
Components: OpenGL
VK-GL-CTS issue: 1609
Affects:
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_types
Change-Id: I33652ac447c0a536bebc8175f34abee45ad1cd2e
Alexander Galazin [Fri, 15 Mar 2019 08:44:37 +0000 (09:44 +0100)]
Merge vk-gl-cts/opengl-cts-4.6.0 into vk-gl-cts/master
Change-Id: I89bd5367fae5953ff5e789542dba7e55a8526ab1
Lionel Landwerlin [Fri, 1 Mar 2019 17:35:12 +0000 (17:35 +0000)]
Drop handwritten toString code
Change-Id: I801cbe14f7bdd571ba8f19242427a071c1c3daea
Components: Vulkan
Boris Zanin [Mon, 11 Feb 2019 12:33:56 +0000 (13:33 +0100)]
Add SPIR-V ids abuse tests
Add tests:
* dEQP-VK.spirv_assembly.instruction.compute.spirv_ids_abuse.*
* dEQP-VK.spirv_assembly.instruction.graphics.spirv_ids_abuse.*
Components: vulkan
VK-GL-CTS issue: 1583
Change-Id: I8cbb94616fc9175de36daf6804cde9b680284aa6
Arkadiusz Sarwa [Mon, 21 Jan 2019 14:50:34 +0000 (15:50 +0100)]
Fix the limitation in allocation test
Change removes the limitation for number of allocations
in the test.
Components: Vulkan
VK-GL-CTS issue: 1569
Affects:
dEQP-VK.api.device_init.create_instance_device_intentional_alloc_fail
Change-Id: I038fcfcae46a6baaf691163166c74ea0d3831043
Alexander Galazin [Wed, 6 Mar 2019 12:35:07 +0000 (12:35 +0000)]
Merge vk-gl-cts/vulkan-cts-1.1.3 into vk-gl-cts/master
Change-Id: I8b085fc2df478a10babc34d753e9e10613dc8929
Alexander Galazin [Tue, 5 Mar 2019 16:57:27 +0000 (16:57 +0000)]
Merge vk-gl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: Ia68d7a02991fe815d1a311f59f3a5928f995069c
Alexander Galazin [Tue, 5 Mar 2019 16:09:54 +0000 (16:09 +0000)]
Merge vk-gl-cts/vulkan-cts-1.1.1 into vk-gl-cts/vulkan-cts-1.1.2
Change-Id: Iaff35efaad77acdd183dd07161fa0da31faaeac2
Alexander Galazin [Tue, 5 Mar 2019 15:41:47 +0000 (15:41 +0000)]
Merge vk-gl-cts/vulkan-cts-1.1.0 into vk-gl-cts/vulkan-cts-1.1.1
Change-Id: I91653c9399920b5e965597c6e4b6006d3490d883
Alexander Galazin [Tue, 5 Mar 2019 15:05:48 +0000 (15:05 +0000)]
Merge vk-gl-cts/vulkan-cts-1.0.2 into vk-gl-cts/vulkan-cts-1.1.0
Change-Id: I0317d6d414441f536e8255db7143e57eeea3448e
Alexander Galazin [Wed, 27 Feb 2019 09:46:39 +0000 (10:46 +0100)]
Notice of withdrawal of Vulkan CTS 1.1.0.x
Components: Vulkan
Change-Id: I5d6c3009267ed2d50cdf6167125b574fb6dcd07a
Igor Ostrowski [Thu, 28 Feb 2019 16:15:12 +0000 (17:15 +0100)]
Fix buffer RAW hazards in synchronization tests
Missing barrier for buffers in semaphore tests.
Affects:
dEQP-VK.synchronization.op.single_queue.semaphore.write_*_read_*.buffer_*
Components: Vulkan
VK-GL-CTS issue: 1633
Change-Id: I0f4ffed00e28816496948d8167e08bbbed999b79
(cherry picked from commit
caef94e99677677cc1aec4a775c1cb757d53f221)
Sandeep Shinde [Tue, 27 Nov 2018 13:36:00 +0000 (19:06 +0530)]
Add tests for VK_KHR_surface_protected_capabilities
Add new tests, which do basic query for functionality provided
by VK_KHR_surface_protected_capabilities extension.
Modify tests to make use of VK_KHR_surface_protected_capabilities
extension to decide whether to run or not. These tests should only be
ran when VkSurfaceCapabilityProtectedKHR.supportsProtected is
reported as VK_TRUE otherwise return as NOT_SUPPORTED because protected
VkSurface can not be displayed on screen through WSI swapchain.
New tests:
dEQP-VK.wsi.xlib.surface.query_protected_capabilities
dEQP-VK.wsi.xcb.surface.query_protected_capabilities
dEQP-VK.wsi.wayland.surface.query_protected_capabilities
dEQP-VK.wsi.mir.surface.query_protected_capabilities
dEQP-VK.wsi.android.surface.query_protected_capabilities
dEQP-VK.wsi.win32.surface.query_protected_capabilities
dEQP-VK.wsi.macos.surface.query_protected_capabilities
Affected tests:
dEQP-VK.api.info.instance.extensions
dEQP-VK.protected_memory.interaction.wsi.xlib.swapchain.render.basic
dEQP-VK.protected_memory.interaction.wsi.xcb.swapchain.render.basic
dEQP-VK.protected_memory.interaction.wsi.wayland.swapchain.render.basic
dEQP-VK.protected_memory.interaction.wsi.mir.swapchain.render.basic
dEQP-VK.protected_memory.interaction.wsi.android.swapchain.render.basic
dEQP-VK.protected_memory.interaction.wsi.win32.swapchain.render.basic
dEQP-VK.protected_memory.interaction.wsi.android.swapchain.render.basic
Components: Vulkan
VK-GL-CTS issue: 1466
Change-Id: I872281801dd935f52c0e999e0c0c2af8a4b8789a
(cherry picked from commit
2d64b282564a754457e4450f34aa8790242ca789)
Slawomir Cygan [Fri, 1 Mar 2019 14:45:39 +0000 (15:45 +0100)]
Fix context creation in robust_buffer_access_behavior test
Move the context creation routine to iterate() method of
tests cases, to avoid overlapping many contexts where
all tests case constructors are fired at once.
Components: OpenGL
VK-GL-CTS Issue: 1629
Affects:
KHR-GL4*.robust_buffer_access_behavior.*
Change-Id: I28658b41891437ef60a5bfd5d0a19b80342e9f1f
Piers Daniell [Fri, 15 Feb 2019 23:47:55 +0000 (16:47 -0700)]
Add testing for VK_EXT_ycbcr_image_arrays
Adds basic testing for VK_EXT_ycbcr_image_arrays by adding
new "array" variants to the ycbcr format tests. These array
variants check whether VK_EXT_ycbcr_image_arrays is
supported and wither the particular image format, usage,
tiling and creation flags allow more than 1 array layers
to be created.
If so, a 2 layer image is created, and the second layer is
populated with the input data. Then the shader does a
texture lookup of the second layer and outputs
that into the result image.
Affects:
dEQP-VK.ycbcr.format.*
Change-Id: I801cbe14f7bdd571ba8f192278a7a071c1c3daea
Components: Vulkan
Toni Merilehti [Thu, 10 Jan 2019 07:52:44 +0000 (09:52 +0200)]
Add tests for pointSize with clamping
These tests verify that the rasterized point size is equal to
the specified pointSize or clamped to the maximum device limit,
pointSizeRange[1].
New tests:
dEQP-VK.rasterization.primitive_size.points.*
Components: Vulkan
VK-GL-CTS issue: 1504
Change-Id: I887d938a2aabde1671c14ef0ee6aff15a908fd1e
Andres Gomez [Thu, 3 Jan 2019 09:21:48 +0000 (11:21 +0200)]
GL_ARB_enhanced_layouts: fix arrays in {G,TC,TE}S
Several negative tests were reporting a misleading fail due to
mismatching output array dimensions in the TCS, TES and GS interfaces.
Components: OpenGL
VK-GL-CTS issue: 1606
Affects:
KHR-GL44.enhanced_layouts.output_component_aliasing
KHR-GL44.enhanced_layouts.varying_block_automatic_member_locations
KHR-GL44.enhanced_layouts.varying_component_of_invalid_type
KHR-GL44.enhanced_layouts.varying_component_without_location
KHR-GL44.enhanced_layouts.varying_exceeding_components
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_auxiliary_storage
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_interpolation
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_types
KHR-GL44.enhanced_layouts.varying_location_limit
KHR-GL44.enhanced_layouts.varying_structure_member_location
Change-Id: I7450cdd41b72b8aca0c6e4638332eaa56a1ed954
Andres Gomez [Thu, 3 Jan 2019 10:07:02 +0000 (12:07 +0200)]
GL_ARB_enhanced_layouts: no static use of inputs
Currently we are testing bogus inputs without a matching counterpart
in the output interface of the previous shader. This is needed since,
otherwise, having a matching output would mean that we would have to
introduce the same error we are trying to test in the input
interface and that could lead to a misleading linking error.
However, not having an output counterpart can also lead to a
misleading linking error. We workaround this by not making a static
use of the tested input.
From page 47 (page 53 of the PDF) of the GLSL 4.60 v.5 spec:
" Only the input variables that are statically read need to be
written by the previous stage; it is allowed to have superfluous
declarations of input variables."
Additionally, make us of the new debugging macro to ease checking that
we are testing just the correct and only cause for a failure report.
Components: OpenGL
VK-GL-CTS issue: 1605
Affects:
KHR-GL44.enhanced_layouts.varying_block_automatic_member_locations
KHR-GL44.enhanced_layouts.varying_block_member_locations
KHR-GL44.enhanced_layouts.varying_component_of_invalid_type
KHR-GL44.enhanced_layouts.varying_component_without_location
KHR-GL44.enhanced_layouts.varying_exceeding_components
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_auxiliary_storage
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_interpolation
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_types
KHR-GL44.enhanced_layouts.varying_structure_member_location
KHR-GL44.enhanced_layouts.xfb_input
Change-Id: I7dc136b34747f40b25b7cc2b6e3f35f029f701f7
Andres Gomez [Fri, 28 Dec 2018 18:52:13 +0000 (20:52 +0200)]
GL_ARB_enhanced_layouts: add missing out varyings
The test was "passing" due to a different error than the one expected
by the test: there were missing output varyings to be able to match
the tested inputs.
Components: OpenGL
VK-GL-CTS issue: 1604
Affects:
KHR-GL44.enhanced_layouts.input_component_aliasing
Change-Id: I038bdc3a08ed1d458c8b0988227307c5f0f3f104
Andres Gomez [Thu, 20 Dec 2018 14:31:14 +0000 (16:31 +0200)]
GL_ARB_enhanced_layouts: correct usage of "flat"
Multiple negative tests were failing due to errors in the usage of the
flat interpolation qualifier. Therefore, the tests were "passing"
while the expected error was a different one than the one reported by
the test.
Additionally, make us of the new debugging macro to ease checking that
we are testing just the correct and only cause for a failure report.
Components: OpenGL
VK-GL-CTS issue: 1603
Affects:
KHR-GL44.enhanced_layouts.input_component_aliasing
KHR-GL44.enhanced_layouts.output_component_aliasing
KHR-GL44.enhanced_layouts.varying_component_of_invalid_type
KHR-GL44.enhanced_layouts.varying_component_without_location
KHR-GL44.enhanced_layouts.varying_exceeding_components
KHR-GL44.enhanced_layouts.varying_location_aliasing_with_mixed_types
KHR-GL44.enhanced_layouts.varying_location_limit
Change-Id: I63f2b11acadfb0b3e42b7e0f176421eaff4da482
Andres Gomez [Thu, 3 Jan 2019 13:19:17 +0000 (15:19 +0200)]
GL_ARB_enhanced_layouts: no def in untested stage
Currently we are trying to match the definition of the output block
with the input block. In a negative test this has the problem that we
cannot actually match without adding the same error we are trying to
test in both interfaces. Therefore, as it is right now, even if the
tested error wouldn't happen, a misleading linking error will happen.
We avoid this by removing the input definition when testing
outputs (no need to have them at all) and, in the reverse situation,
additionally, by not doing static use of the defined input variable.
Additionally, this simplifies the test a lot.
Finally, added a debugging macro to ease checking that we are testing
just the correct and only cause for a failure report.
Components: OpenGL
VK-GL-CTS issue: 1602
Affects:
KHR-GL44.enhanced_layouts.varying_block_member_locations
Change-Id: Ia2c0ba705e975817999aaa16c1ce129d616540f6
Igor Ostrowski [Thu, 28 Feb 2019 16:15:12 +0000 (17:15 +0100)]
Fix buffer RAW hazards in synchronization tests
Missing barrier for buffers in semaphore tests.
Affects:
dEQP-VK.synchronization.op.single_queue.semaphore.write_*_read_*.buffer_*
Components: Vulkan
VK-GL-CTS issue: 1633
Change-Id: I0f4ffed00e28816496948d8167e08bbbed999b79
Alexander Galazin [Fri, 1 Mar 2019 11:07:51 +0000 (12:07 +0100)]
Whitelist Vulkan CTS 1.1.3.1
Components: Vulkan
Affects: dEQP-VK.api.driver_properties.properties
Change-Id: Ic8d6afa3998a4d77d2c00c10ee9075f62febf5aa
Alexander Galazin [Thu, 28 Feb 2019 16:52:50 +0000 (17:52 +0100)]
Remove unnecessary 1.1.3 mustpass sources
Change-Id: I3f7cc4649954f784736c8529fc9a24761d6da01d
Alexander Galazin [Thu, 28 Feb 2019 16:24:55 +0000 (17:24 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.3 vk-gl-cts/master
Change-Id: Iad6b3f1c809ac70182f11c00d2e88b88b19e4fb0
Alexander Galazin [Thu, 28 Feb 2019 16:23:25 +0000 (17:23 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: I7f44646072e49414e863e6a4e6bb9760477dccb8
Alexander Galazin [Thu, 28 Feb 2019 16:17:02 +0000 (17:17 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.1 into vk-gl-cts/vulkan-cts-1.1.2
Change-Id: Id1dfb48db9c7c5ad1d4260e4595617723034af04
Alexander Galazin [Thu, 28 Feb 2019 15:49:11 +0000 (16:49 +0100)]
Exclude few rasterization tests
Components: Vulkan
Affects:
dEQP-VK.rasterization.interpolation.basic.lines_wide
dEQP-VK.rasterization.interpolation.projected.line_strip_wide
dEQP-VK.rasterization.flatshading.lines_wide
VK-GL-CTS issue: 1274
Change-Id: I4771bc1729ccd6eb39e291cb26a5db5b42688140
Alexander Galazin [Thu, 28 Feb 2019 14:47:47 +0000 (15:47 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.3 into vk-gl-cts/master
Change-Id: I866d7a1ba446f0482d1b26823c97bb5afc49ad7a
Alexander Galazin [Thu, 28 Feb 2019 14:37:46 +0000 (15:37 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: I01321e70bb29b8a21ed2f730381ea44f71f12c9b
Alexander Galazin [Thu, 28 Feb 2019 14:34:57 +0000 (15:34 +0100)]
Merge vk-gl-cts/github-vulkan-cts-1.1.3 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: I354674f48a6d88f95199865ceb8fe64c4100e1cf
Toni Merilehti [Wed, 27 Feb 2019 08:41:33 +0000 (10:41 +0200)]
Fix validation errors in dEQP-VK.tessellation.*
In multiple tests memory allocations are invalidated or flushed using
a size that on some devices is not a multiple of nonCoherentAtomSize
device limit, causing validation errors. This fix uses helper functions
that invalidate or flush the whole allocation where the size of the
memory being invalidated/flushed equals the size of the allocation.
Affects:
dEQP-VK.tessellation.*
Components: Vulkan
VK-GL-CTS issue: 1620
Change-Id: I3c0aed7f749693808331a1b430ad2cb28b138699
Alexander Galazin [Thu, 28 Feb 2019 14:19:04 +0000 (15:19 +0100)]
Merge pull request #143 from jrprice/utb-glsl-type
Fix image type for uniform texel buffers
Liam Middlebrook [Fri, 22 Feb 2019 21:22:24 +0000 (13:22 -0800)]
Fix SpvWorkgroupMemoryTests float32 result check
Fix a bug in spirv_assembly.instruction.compute.workgroup_memory.float32
where the output values were being compared on a byte-level and not
compared as floating-point values.
Affects:
dEQP-VK.spirv_assembly.instruction.compute.workgroup_memory.float32
Components: Vulkan
VK-GL-CTS Issue: 1625
Change-Id: Ia274e5f08796ebf8e4a6fa78e7df377a80e5a25f
Tom Cooper [Fri, 8 Feb 2019 14:14:40 +0000 (14:14 +0000)]
Fixes YCbCr create flag requirements for image format properties tests
YCbCr formats are not required to support
VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT.
Components: Vulkan
Affects: dEQP-VK.api.info.image_format_properties.*
VK-GL-CTS Issue: 1592
Change-Id: I140f6b93a337d325fd908259f3da2dc1f4d251d9
Slawomir Cygan [Thu, 21 Feb 2019 15:10:07 +0000 (16:10 +0100)]
Use valid deviceMask in vkAcquireNextImage2KHR
As the test uses the default device (without explicit device groups),
there is only one device in the group, with index 0.
Given that, the only valid deviceMask is 1 (not 0xffffffff).
Components: Vulkan
VK-GL-CTS Issue: 1623
Affects: dEQP-VK.wsi.win32.swapchain.render.basic2
Change-Id: I93813248fbeebc2787acdfe550d42588f60e8f7d
Igor Ostrowski [Wed, 20 Feb 2019 10:15:54 +0000 (11:15 +0100)]
Fix device mask in swapchain tests
All elements of pCommandBufferDeviceMasks must be valid device masks
Affects:
dEQP-VK.wsi.*.swapchain.render.device_group
Components: Vulkan
VK-GL-CTS issue: 1618
Change-Id: Ic3857672a99b3d4039b26cd0139c08bca7a0e5da
Igor Ostrowski [Fri, 15 Feb 2019 14:33:42 +0000 (15:33 +0100)]
Fix RAW and WAW hazards in pipeline barrier tests.
Test was not handling correctly internal state of the visibility and availability operations.
Both access scopes of the barrier must be set correctly to unlock such usage of the resource.
Affects:
dEQP-VK.memory.pipeline_barrier.*
Components: Vulkan
VK-GL-CTS issue: 1589
Change-Id: I7a778dbee8109f060b88beee625ca15de01c7364
asokolow [Wed, 6 Feb 2019 09:12:28 +0000 (10:12 +0100)]
Create context with CONTEXT_ROBUST for robust buffer access tests
These tests exercise functionality that is not available in default
context provided by the framework. New context, with CONTEXT_ROBUST
(WGL|GLX_CONTEXT_ROBUST_ACCESS_BIT_ARB) flag is created for these
tests.
Component: OpenGL
VK-GL-CTS Issue: 1588
Affects:
KHR-GL4*.robust_buffer_access_behavior.*
Change-Id: Ie698a6a434426bf147a705cc487b4fbe560a79c7
Alexander Galazin [Tue, 26 Feb 2019 19:40:18 +0000 (20:40 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.3 into vk-gl-cts/master
Change-Id: I092923bd34672e06802545333b2aea7c630fbf70
Alexander Galazin [Tue, 26 Feb 2019 18:44:27 +0000 (19:44 +0100)]
Merge vk-gkl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: I6acb7ecd862fd48e3602301e4d05394b4a34489a
Alexander Galazin [Tue, 26 Feb 2019 16:53:28 +0000 (17:53 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.1 into vk-gl-cts/vulkan-cts-1.1.2
Change-Id: Ic711984d0039550239e56cefd30e735da866f524
James Price [Mon, 25 Feb 2019 16:11:44 +0000 (16:11 +0000)]
Fix image type for uniform texel buffers
This fixes issues described in #139 but in additional test categories,
in the same manner as in commit 69278de.
Affects:
dEQP-VK.binding_model.descriptorset_random.sets4.*
dEQP-VK.api.buffer_view.access.*
dEQP-VK.memory.pipeline_barrier.*uniform_texel_buffer.*
dEQP-VK.robustness.buffer_access.*.texel_copy.*
Alexander Galazin [Tue, 26 Feb 2019 16:19:23 +0000 (17:19 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.0 into vk-gl-cts/vulkan-cts-1.1.1
Change-Id: Ib3a1ff276813033d0bfc87150266e4ff848aa290
Alexander Galazin [Tue, 26 Feb 2019 14:38:00 +0000 (15:38 +0100)]
Merge vk-gl-cts/vulkan-cts-1.0.2 into vk-gl-cts/vulkan-cts-1.1.0
Change-Id: Ibc6149bcd2518049216704334a23d90ea572c446
Boris Zanin [Fri, 22 Feb 2019 10:55:43 +0000 (11:55 +0100)]
Disable SPIR-V ids optimization
The default for the SPIR-V assembler is to compress IDs.
So even if you have %
111111111 it will reassign that to the
next unused ID (a bump allocator). To disable this I need
to specify the equivalent of the --preserve-numeric-ids
option to the assembler. After discussion with Alex I specify
SPV_TEXT_TO_BINARY_OPTION_PRESERVE_NUMERIC_IDS for all tests.
Affected tests:
* dEQP-VK.*
Components: vulkan
VK-GL-CTS issue: 1583
Change-Id: I941adf5d5cdb964eb4dff46afa75b01e089d3061
ygole [Tue, 15 Jan 2019 13:49:31 +0000 (19:19 +0530)]
Check if CTS has platform display for wsi-type
Vulkan driver can expose multiple VK_KHR_{platform}_surface extensions
and it's app responsibility to create platform display then create the
surface and pass it to vkCreate{platform}SurfaceKHR. But if CTS does
not have display for requested wsi type and extension is exposed, CTS
reports it as failure.
To fix this, if function createWsiDisplay fails then check whether CTS
has platform display available for requested wsi-type and if it does
then only report this as failure otherwise report it as unsupported.
Affects: dEQP-VK.wsi.*
Components: Vulkan, Framework
VK-GL-CTS issue: 1558
Change-Id: I41aabc2e77cfc6e730b5a95dde746d8ea8152d2b
(cherry picked from commit
b7efacd7b320d2b2c3b8b75cf98c9979b5a29fe9)
Alexander Galazin [Fri, 22 Feb 2019 13:22:13 +0000 (14:22 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.3 into vk-gl-cts/master
Change-Id: If127ebc2efa5fcc3c48f5d4fa47a7bfa181bfa1c
Alexander Galazin [Fri, 22 Feb 2019 12:07:19 +0000 (13:07 +0100)]
Update glslang, SPIR-V tools and headers
Components: Framework
Change-Id: I091d24cbb521f16a52219e2daf9ec66ed376f748
Alexander Galazin [Fri, 22 Feb 2019 12:36:31 +0000 (13:36 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: I75a8948cb99a649cc84d2f26f1f1a49e3d5a6167
Steve Hill [Fri, 18 Jan 2019 09:19:17 +0000 (09:19 +0000)]
Add control for subpixel bits to reference rasterizer
The reference rasterizer assumed that subpixel bits was 8,
and this could lead to issues on some platforms.
This change makes it mandatory to specify the number of
subpixel bits required when using the reference rasterizer.
EGL, OpenGL and Vulkan tests that use the reference rasterizer
are changed to supply the platform-advertised subpixel bits.
Given the invasive nature of this change, the affects list
is extremely conservative.
Affects:
dEQP-VK*
dEQP-GL*
dEQP-EGL*
Components: Vulkan, OpenGL, EGL, Framework.
VK-GL-CTS issue: 1566
Change-Id: I6e89cc6e3b71b7d2d7fb02c4c21857ec4ad0146c
Paul Thomson [Wed, 6 Feb 2019 09:49:18 +0000 (09:49 +0000)]
Add dEQP-VK.graphicsfuzz.fragcoord-control-flow
Components: Vulkan
New Tests:
dEQP-VK.graphicsfuzz.fragcoord-control-flow
Change-Id: Id431f82e8b577c029b241ee89f3699e197131b00
Toni Merilehti [Thu, 14 Feb 2019 14:14:24 +0000 (16:14 +0200)]
Define point sizes in dEQP-VK.query_pool.* tests
This adds missing point sizes to vertex and geometry shaders under
dEQP-VK.query_pool.* when primitive topology is set to POINT_LIST.
Affects:
dEQP-VK.query_pool.*
Components: Vulkan
VK-GL-CTS issue: 1598
Change-Id: I02918a7662a52b3495fb872d1d5ac29e5753ecfa
Ari Suonpaa [Mon, 18 Feb 2019 11:14:24 +0000 (13:14 +0200)]
Fix zero height clear rectangle
Some of the layered rendering tests are clearing
two rectangles by using half of the frame buffer
height. In case of 1D textures the height is one,
making the clear rectangle height zero. This was
taken into account by rounding the height in one
of the rectangles up. But the remaining zero
height rectangle is still invalid and is now
removed from the list of clear rectangles.
Affects:
dEQP-VK.geometry.layered.*.secondary_cmd_buffer*
Components: Vulkan
VK-GL-CTS issue: 1600
Change-Id: I6e58d9f343019fe1bc9f7a1920d0515e252e81ec
Graeme Leese [Fri, 22 Feb 2019 10:48:45 +0000 (10:48 +0000)]
Fix spelling of error message
Components: Vulkan
Affects: dEQP-VK.api.command_buffers.record_simul_use_*
Change-Id: I2be44e485461d4c7c1009e8abedaa378aaf9ebf1
Lingfeng Yang [Fri, 8 Feb 2019 15:36:00 +0000 (07:36 -0800)]
Fix stack underflow in incremental present test
This uses the current object's m_queueFamilyIndex instead of a queue
family index that is on the stack, avoiding using a stale stack address
when the test runs.
VK-GL-CTS issue: 1585
Affects:
dEQP-VK.wsi.*.incremental_present.*
Components: Vulkan
Change-Id: I80228651b799d3444676cdcbf5cc845bcb195fe9
Paul Thomson [Wed, 6 Feb 2019 10:31:00 +0000 (10:31 +0000)]
Add dEQP-VK.graphicsfuzz.fragcoord-control-flow-2
Components: Vulkan
New Tests:
dEQP-VK.graphicsfuzz.fragcoord-control-flow-2
Change-Id: I452a587be37391da94c0a91b38bfafc894c48dc8
Jeff Bolz [Sat, 17 Nov 2018 20:16:19 +0000 (14:16 -0600)]
VK_EXT_buffer_device_address tests
Components: Vulkan
New Tests:
dEQP-VK.memory_model.*phys*
dEQP-VK.binding_model.buffer_device_address.*
dEQP-VK.spirv_assembly.instruction.compute.physical_pointers.*
dEQP-VK.ssbo.phys.layout*
Change-Id: Ida85e47c749475009cf281918c8149475f94da7d
Lionel Landwerlin [Wed, 23 Jan 2019 18:29:34 +0000 (18:29 +0000)]
Fix swapchain mutable tests buffer allocations
We're seeing failure on our implementation and those seem to be
related to the fact that some buffers are allocated with one VkDevice
and used with another VkDevice. This raises errors in the validation
layers :
Validation(ERROR): msg_code:
385926663:
[ VUID-vkBindBufferMemory-memory-parent ] Object: 0x6 (Type = 8) |
Object 0x6 was not created, allocated or retrieved from the correct
device. The spec valid usage text states 'memory must have been
created, allocated, or retrieved from device'
Affects: dEQP-VK.image.swapchain_mutable.*
Change-Id: I4d3c62dace2d259061382d3014deb05bc4eac9d7
(cherry picked from commit
b48fc89ada2a1b88796d1354d10210928b1fbf0d)
Lisa Wu [Wed, 20 Feb 2019 13:58:11 +0000 (14:58 +0100)]
Check shaderInt64 feature support in memory tests
Not all vulkan implementations support int64 data type in shaders,
dEQP-VK.memory_model.* tests should check support before using "int64"
in the shader.
Affects: dEQP-VK.memory_model.*.u64.*
Components: Vulkan
VK-GL-CTS issue: 1621
Change-Id: Idefe662a7327708898b01777f14f6ca9637a35f3
Alexander Galazin [Thu, 21 Feb 2019 10:57:43 +0000 (11:57 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.3 into vk-gl-cts/master
Change-Id: I6d68022af70ffee1df11b38500129f2666f3dd7a
Alexander Galazin [Thu, 21 Feb 2019 10:32:14 +0000 (11:32 +0100)]
Merge vk-gl-cts/aosp-deqp-dev into vk-gl-cts/master
Change-Id: I90d628347dbe5c15eef39a874898135e3809cfe2
Alexander Galazin [Thu, 21 Feb 2019 09:40:56 +0000 (10:40 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.2 into vk-gl-cts/vulkan-cts-1.1.3
Change-Id: Iaf38fdb099fc5777170b6d3bdef9e2fcdd5ea3bb
Alexander Galazin [Thu, 21 Feb 2019 09:08:51 +0000 (10:08 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.1 into vk-gl-cts/vulkan-cts-1.1.2
Change-Id: I340cd7f2e1cd8a98c98c0b9018a6648dba6712cc
Alexander Galazin [Thu, 21 Feb 2019 08:39:43 +0000 (09:39 +0100)]
Merge vk-gl-cts/vulkan-cts-1.1.0 into vk-gl-cts/vulkan-cts-1.1.1
Change-Id: I404c995c42188a88a080ba5b27c3075e5d746f7f
Alex Walters [Tue, 12 Feb 2019 17:50:27 +0000 (17:50 +0000)]
Fragment input components limit includes position
The Vulkan limits maxFragmentInputComponent is inclusive of any
components that are being used up by the built-in interface block.
This means that the test of n components should consist of 4 components
for the position and (n - 4) user defined components.
The test should also check the maxVertexOutputComponent limit as
technically there is no implied >= requirement.
Affects:
dEQP-VK.glsl.limits.near_max.fragment_input.components_*
Component: Vulkan
VK-GL-CTS Issue: 1597
Change-Id: I58adbbbaaa94dd185b024f63519dac7daf5e4b3c
(cherry picked from commit
8b5781b8e7a4564ddec376828a16fd89fb8e3227)
Dan Sinclair [Thu, 3 Jan 2019 20:37:57 +0000 (15:37 -0500)]
Add Amber as a test engine
This CL adds amber as a possible testing engine for the CTS.
Change-Id: I5d1d7e6a03d9b66e3efc196ad488d66fd0333fc1
Tim Van Patten [Fri, 11 Jan 2019 18:42:16 +0000 (11:42 -0700)]
Fix Android dEQP builds when linking against and embedding ANGLE
The Android dEQP build is failing to link against ANGLE when using the
option '--angle-path'. This fix correctly clears the necessary CMAKE
variables so the find_library() call will search for the ANGLE libraries
during an Android build.
Components: Android dEQP
Google bug:
80239516
Change-Id: I9ceb82e47becda56ff7ace77f999f37c70dd97b0
ygole [Tue, 15 Jan 2019 13:49:31 +0000 (19:19 +0530)]
Check if CTS has platform display for wsi-type
Vulkan driver can expose multiple VK_KHR_{platform}_surface extensions
and it's app responsibility to create platform display then create the
surface and pass it to vkCreate{platform}SurfaceKHR. But if CTS does
not have display for requested wsi type and extension is exposed, CTS
reports it as failure.
To fix this, if function createWsiDisplay fails then check whether CTS
has platform display available for requested wsi-type and if it does
then only report this as failure otherwise report it as unsupported.
Affects: dEQP-VK.wsi.*
Components: Vulkan, Framework
VK-GL-CTS issue: 1558
Change-Id: I41aabc2e77cfc6e730b5a95dde746d8ea8152d2b
Paul Thomson [Fri, 8 Feb 2019 12:14:51 +0000 (12:14 +0000)]
Add dEQP-VK.graphicsfuzz.while-inside-switch
Components: Vulkan
New Tests:
dEQP-VK.graphicsfuzz.while-inside-switch
Change-Id: I06500d87906efc382e676fc7f6df678bebe4e0d1
Yu-Jun Li [Wed, 6 Feb 2019 17:47:52 +0000 (09:47 -0800)]
Fix mismatch between VS outputs and GS inputs
VS was outputing gl_Position while GS expected
a block.
Components: Vulkan
VK-GL-CTS issue: 1594
Affects:
dEQP-VK.spirv_assembly.instruction.graphics.module.same_module_geom
Change-Id: Ib527cfda04fab0a206a45eb747b7e7751e71baa4
Alex Walters [Tue, 12 Feb 2019 17:50:27 +0000 (17:50 +0000)]
Fragment input components limit includes position
The Vulkan limits maxFragmentInputComponent is inclusive of any
components that are being used up by the built-in interface block.
This means that the test of n components should consist of 4 components
for the position and (n - 4) user defined components.
The test should also check the maxVertexOutputComponent limit as
technically there is no implied >= requirement.
Affects:
dEQP-VK.glsl.limits.near_max.fragment_input.components_*
Component: Vulkan
VK-GL-CTS Issue: 1597
Change-Id: I58adbbbaaa94dd185b024f63519dac7daf5e4b3c
Alexander Galazin [Thu, 14 Feb 2019 18:56:07 +0000 (13:56 -0500)]
Revert "Fix subpixel precision for line geometry generation"
This reverts commit
3116016d8e0e4582396d67a1286aa3a6815a3332.
VK-GL-CTS issue: 1582, 1274
Affects:
dEQP-VK.rasterization.*line*
dEQP-GLES*.functional.rasterization.*line*
Components: Framework
Change-Id: I5e1fbc948f5784656523c37924ca746c6b6aa5a8
Alexander Galazin [Fri, 8 Feb 2019 12:46:13 +0000 (13:46 +0100)]
Raise VS supported version to 2015
Drop support for VS2013, require at least VS2015
Components: Vulkan, OpenGL
Change-Id: I2ee814d69b4483dbdad9a579575c8db68548591a