Name |
Date |
Size |
#Lines |
LOC |
||
---|---|---|---|---|---|---|
.. | - | - | ||||
conan/ | 12-May-2024 | - | 39 | 28 | ||
pkgconfig/ | 12-May-2024 | - | 56 | 42 | ||
BUILD.gn | D | 12-May-2024 | 3 KiB | 147 | 132 | |
CMakeLists.txt | D | 12-May-2024 | 1.2 KiB | 33 | 31 | |
README.md | D | 12-May-2024 | 1.2 KiB | 23 | 19 | |
test_cl.h.c | D | 12-May-2024 | 726 | 26 | 7 | |
test_cl_egl.h.c | D | 12-May-2024 | 734 | 26 | 7 | |
test_cl_ext.h.c | D | 12-May-2024 | 734 | 26 | 7 | |
test_cl_ext_intel.h.c | D | 12-May-2024 | 746 | 26 | 7 | |
test_cl_gl.h.c | D | 12-May-2024 | 732 | 26 | 7 | |
test_cl_gl_ext.h.c | D | 12-May-2024 | 740 | 26 | 7 | |
test_cl_half.h.c | D | 12-May-2024 | 4 KiB | 127 | 87 | |
test_cl_icd.h.c | D | 12-May-2024 | 986 | 32 | 13 | |
test_cl_platform.h.c | D | 12-May-2024 | 744 | 26 | 7 | |
test_cl_version.h.c | D | 12-May-2024 | 742 | 26 | 7 | |
test_headers.c | D | 12-May-2024 | 28.5 KiB | 639 | 498 | |
test_opencl.h.c | D | 12-May-2024 | 734 | 26 | 7 |
README.md
1OpenCL-Headers/tests README 2=========================== 3 4The test_headers.c test is designed to make sure that the various cl_typen types 5work and conform to expectation for recent versions of cl_platform.h. Conforming 6to these expectations make use of these types practical for developers writing 7portable code. 8 9The various tests ending in .h.c are there to verify that the various OpenCL 10headers can compile stand alone. That is to ensure that they may be used a la 11carte. This provides developers a lifeline in the case that some unneeded part 12of OpenCL (e.g. cl/gl sharing) brings in a pile of symbols (e.g. all of OpenGL) 13that collides with other headers needed by the application. It is also poor form 14to require headers to be included in a particular order, especially if multiple 15systems require they be included in mutually incompatible order. So, here we 16require that each header can be used standalone so that the order is irrelevant. 17 18We also check to make sure that the headers don't cause spurious warnings. These 19tests are intended to be compiled using the most stringent compiler flags 20available for the platform, within reason. All warnings should be errors and 21extra warnings that it is expected developers are likely to use should be turned 22on. 23