The table below describes the list of built-in math functions. These functions can take scalar or vector arguments. Click an item in the table for details about that function.
The table below describes the list of built-in math functions that are defined with the half_
or native_
prefix
The built-in math functions are not affected by the prevailing rounding mode in the calling environment, and always return the same value as they would if called with the round to nearest even rounding mode.
The regular built-in math functions can take scalar or vector arguments. For any specific use of a function, the actual type has to be the same for all arguments and the return type, unless otherwise specified. For more information, see the reference page for a specific function.
The built-in math functions are extended with cl_khr_fp64 to include appropriate versions of functions that take double and double{2|3|4|8|16} as arguments and return values. They are also extended with cl_khr_fp16 to include appropriate versions of functions that take half and half{2|3|4|8|16} as arguments and return values.
The vector versions of the math functions operate component-wise. The description is per-component.
Support for denormal values is optional for half_
functions. The half_
functions may return any result allowed by section 7.5.3, even when -cl-denorms-are-zero is not in force. Support for denormal values is implementation-defined for native_
functions.
The math functions that are defined with the half_
prefix are implemented with a minimum of 10-bits of accuracy i.e. an ULP value <= 8192 ulp.
The math functions that are defined with the native_
prefix may map to one or more native device instructions and will typically have better performance compared to the corresponding functions (without the native_
prefix) described. The accuracy (and in some cases the input range(s)) of these functions is implementation-defined.