test_3D_2D_array uses max limits of 3D images
for both 3D images and 2D_array.
This leads to testing of sizes larger than
2D array limits.
Use correct CL_MEM_OBJECT_IMAGE_TYPE to avoid
test-cases with invalid sizes.
* Fix WIN compilation and add some clarification.
* Add CLConform_GL_LIBRARIES_DIR CmakeLists variable for GL support
* GL sharing tests - library names justification
* Fix compilation errors function are overridden in glext.h.
* fix cl12 - Add CLConform_GL_LIBRARIES_DIR CmakeLists variable for GL support
M_PI is not part of C99 or C++ and thus aren't provided in all configurations.
This used to be handled in reference_math.c directly but was recently removed.
Just tweak the M_PI handling in the compatibility headers to restore builds.
This change splits up is_extension_available() so that the bulk of it
can be reused for fetching other items of variable-length device
information, such as CL_DEVICE_VERSION.
* Use slice pitch instead of row pitch for 1D arrays.
Fixes fill_image 1Darray
* Use slice pitch instead of row pitch for 1D arrays.
Fixes copy_image 1Darray
Parallel printf tests fail because they use the same file tmp
to capture OpenCL kernel outputs. This patch solves this problem by
using a unique file for each process.
Spir test compares floating-point kernel results bit-by-bit with
correct results. However, for math_brute_force kernels, specification
does not ask for SPIR and OpenCL C path to match bit-to-bit. This patch
reuses ulps threshold from math_brute_force folder for math_brute_force
kernels in spir test.
Signed-off-by: Wenju He <wenju.he@intel.com>
* cl12: Compiler - added missing extensions to compiler_defines_for_extensions.
Updated the list of known extensions to include all extensions referenced in the OpenCL Extension Specification 1.2 - Revision 25 and OpenCL Specification 1.2 - Revision 19 documents.
* Re-added the cl_khr_il_program extension.
This was this was erroneously removed in the previous commit.
* Compiler: Added all known extensions to compiler_defines_for_extensions.
After discussion on the pull request, it was decided to have this test test for all known khr extensions accross all API levels. Some vendors support 2.x extensions on 1.x implementations, so wanted to ensure that the test still covered those cases.
Re-ordered each sub-list so that the order in which each extension appears mirrors that of https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_Ext.html.
For reference: https://github.com/KhronosGroup/OpenCL-CTS/pull/55.
* Compiler: Moved priority and throttle hints to the API-only section of the array in compiler_defines_for_extensions.
* Compiler: Added cl_khr_spirv_no_integer_wrap_decoration to the list of extensions.
There is no mention of this rule that I could find in the
OpenCL 1.2 specification. cl12_trunk was the only branch
with this behaviour.
Signed-off-by: Kévin Petit <kpet@free.fr>
Function verifyOutputBuffer returns non-zero value in case of mismatch.
Return value 'false' means some mismatches are treated as matches. This
commit fix this problem.
The maintenance of the conformance tests is moving to Github.
This commit contains all the changes that have been done in
Gitlab since the first public release of the conformance tests.
Signed-off-by: Kevin Petit <kevin.petit@arm.com>
Performs a single build on Linux using the unified
headers and linking against the ICD.
Also add a build badge to the README.
Signed-off-by: Kevin Petit <kevin.petit@arm.com>
