mirror of
https://github.com/KhronosGroup/OpenCL-CTS.git
synced 2026-03-19 22:19:02 +00:00
2c0abd3f75
Put "run_conformance.py" and all test runner files ".csv" in build directory Put "run_conformance.py" and all test runner files ".csv" in build directory Added steps in CMakeLists.txt to copy the ".csv" files and "run_conformance.py" from 'test_conformance' directory Signed-off-by: bhargavthriler <bhargavthriler@gmail.com> cl12: change binary names to aligned with the test runner files Changed output binary names to match with the test runner files .csv files Signed-off-by: bhargavthriler <bhargavthriler@gmail.com> Removed relative paths, changed comment style Removed relative paths and replaced with CMake variables Changed comment style to match with remaining comment style to maintain consistency changed destination relative path with cmake variable Signed-off-by: bhargavthriler <bhargavthriler@gmail.com> fixed binary name in test runner files Signed-off-by: bhargavthriler <bhargavthriler@gmail.com>
test_conformance/headers README =============================== The test_headers.c test is designed to make sure that the various cl_typen types work and conform to expectation for recent versions of cl_platform.h. Conforming to these expectations make use of these types practical for developers writing portable code. The various tests ending in .h.c are there to verify that the various OpenCL headers can compile stand alone. That is to ensure that they may be used a la carte. This provides developers a lifeline in the case that some unneeded part of OpenCL (e.g. cl/gl sharing) brings in a pile of symbols (e.g. all of OpenGL) that collides with other headers needed by the application. It is also poor form to require headers to be included in a particular order, especially if multiple systems require they be included in mutually incompatible order. So, here we require that each header can be used standalone so that the order is irrelevant. In the .h.c tests, we also check to make sure that the headers don't cause spurious warnings. These tests are intended to be compiled using the most stringent compiler flags available for the platform, within reason. All warnings should be errors and extra warnings that it is expected developers are likely to use should be turned on. The current Makefile includes such flags for a GCC compiler. Implementors are expected to modify these flags and make system as necessary to conform to the local build environment.