5cc337c890
* Add cl_half.h header
* Make shared utility for handling {over,under}flow
* Include stdint.h
* Prefix all new functions with cl_half_
* Address Windows warnings
* Refactor lsb_pos calculation
* Avoid leading double-underscore in header guard
* Update license
* Add tests for cl_half.h
|
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| README.md | ||
| test_cl_egl.h.c | ||
| test_cl_ext_intel.h.c | ||
| test_cl_ext.h.c | ||
| test_cl_gl_ext.h.c | ||
| test_cl_gl.h.c | ||
| test_cl_half.h.c | ||
| test_cl_icd.h.c | ||
| test_cl_platform.h.c | ||
| test_cl_version.h.c | ||
| test_cl.h.c | ||
| test_headers.c | ||
| test_opencl.h.c | ||
OpenCL-Headers/tests 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.
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.