To link a set of compiled program objects and libraries for all the devices or a specific device(s) in the OpenCL context and create a library or executable, call the function
cl_program clLinkProgram( cl_context context, cl_uint num_devices, const cl_device_id* device_list, const char* options, cl_uint num_input_programs, const cl_program* input_programs, void (CL_CALLBACK* pfn_notify)(cl_program program, void* user_data), void* user_data, cl_int* errcode_ret);
context must be a valid OpenCL context.
device_list is a pointer to a list of devices that are in context. If device_list is a
NULLvalue, the link is performed for all devices associated with context for which a compiled object is available. If device_list is a non-
NULLvalue, the link is performed for devices specified in this list for which a compiled object is available.
num_devices is the number of devices listed in device_list.
options is a pointer to a null-terminated string of characters that describes the link options to be used for building the program executable. The list of supported options is as described in Linker Options. If the program was created using clCreateProgramWithBinary and options is a
NULLpointer, the program will be linked as if options were the same as when the program binary was originally built. If the program was created using clCreateProgramWithBinary and options string contains anything other than the same options in the same order (whitespace ignored) as when the program binary was originally built, then the behavior is implementation defined. Otherwise, if options is a
NULLpointer then it will have the same result as the empty string.
num_input_programs specifies the number of programs in array referenced by input_programs.
input_programs is an array of program objects that are compiled binaries or libraries that are to be linked to create the program executable. For each device in device_list or if device_list is
NULLthe list of devices associated with context, the following cases occur:
All programs specified by input_programs contain a compiled binary or library for the device. In this case, a link is performed to generate a program executable for this device.
None of the programs contain a compiled binary or library for that device. In this case, no link is performed and there will be no program executable generated for this device.
All other cases will return a
pfn_notify is a function pointer to a notification routine. The notification routine is a callback function that an application can register and which will be called when the program executable has been built (successfully or unsuccessfully).
user_data will be passed as an argument when pfn_notify is called. user_data can be
If pfn_notify is not
NULL, clLinkProgram does not need to wait for the
linker to complete, and can return immediately once the linking operation can
Once the linker has completed, the pfn_notify callback function is called
which returns the program object returned by clLinkProgram.
The application can query the link status and log for this program object.
This callback function may be called asynchronously by the OpenCL
It is the applications responsibility to ensure that the callback function
If pfn_notify is
NULL, clLinkProgram does not return until the linker
clLinkProgram creates a new program object which contains the library or
The library or executable binary can be queried using
CL_PROGRAM_BINARIES, …) and can be specified
to clCreateProgramWithBinary to create a new program object.
The devices associated with the returned program object will be the list of
devices specified by device_list or if device_list is
NULL it will be
the list of devices associated with context.
The linking operation can begin if the context, list of devices, input programs and linker options specified are all valid and appropriate host and device resources needed to perform the link are available. If the linking operation can begin, clLinkProgram returns a valid non-zero program object.
If pfn_notify is
NULL, the errcode_ret will be set to
the link operation was successful and
CL_LINK_PROGRAM_FAILURE if there is a
failure to link the compiled binaries and/or libraries.
If pfn_notify is not
NULL, clLinkProgram does not have to wait until
the linker to complete and can return
CL_SUCCESS in errcode_ret if the
linking operation can begin.
The pfn_notify callback function will return a
CL_LINK_PROGRAM_FAILURE if the linking operation was successful or not.
Otherwise clLinkProgram returns a
NULL program object with an
appropriate error in errcode_ret.
The application should query the linker status of this program object to
check if the link was successful or not.
The list of errors that can be returned are:
CL_INVALID_CONTEXTif context is not a valid context.
CL_INVALID_VALUEif device_list is
NULLand num_devices is greater than zero, or if device_list is not
NULLand num_devices is zero.
CL_INVALID_VALUEif num_input_programs is zero and input_programs is
NULLor if num_input_programs is zero and input_programs is not
NULLor if num_input_programs is not zero and input_programs is
CL_INVALID_PROGRAMif programs specified in input_programs are not valid program objects.
CL_INVALID_VALUEif pfn_notify is
NULLbut user_data is not
CL_INVALID_DEVICEif any device in device_list is not in the list of devices associated with context.
CL_INVALID_LINKER_OPTIONSif the linker options specified by options are invalid.
CL_INVALID_OPERATIONif the compilation or build of a program executable for any of the devices listed in device_list by a previous call to clCompileProgram or clBuildProgram for program has not completed.
CL_INVALID_OPERATIONif the rules for devices containing compiled binaries or libraries as described in input_programs argument above are not followed.
CL_LINKER_NOT_AVAILABLEif a linker is not available i.e.
CL_DEVICE_LINKER_AVAILABLEspecified in the Device Queries table is set to
CL_LINK_PROGRAM_FAILUREif there is a failure to link the compiled binaries and/or libraries.
CL_OUT_OF_RESOURCESif there is a failure to allocate resources required by the OpenCL implementation on the device.
CL_OUT_OF_HOST_MEMORYif there is a failure to allocate resources required by the OpenCL implementation on the host.
For more information, see the OpenCL Specification
This page is extracted from the OpenCL Specification. Fixes and changes should be made to the Specification, not directly.
Copyright (c) 2014-2020 Khronos Group. This work is licensed under a Creative Commons Attribution 4.0 International License.