CLCREATEPROGRAMWITHB(3clc)

📦
version 1.0~svn33624 · 3 versions
, in ubuntu jammy, ubuntu noble

💖 NAME 💖

clCreateProgramWithBinary — bestie, this is the OpenCL call that makes a program object for a context and loads the binary bits you hand it, specified by binary, straight into that program object. no source code, no compiling from scratch, just vibes and prebuilt bytes. 🦋

This page lives in the OpenCL Manual, section 3clc. Pull up a chair, we're getting into it.

✨ SYNOPSIS ✨

cl_program clCreateProgramWithBinary(cl_context context,
                                     cl_uint num_devices,
                                     const cl_device_id *device_list,
                                     const size_t *lengths,
                                     const unsigned char **binaries,
                                     cl_int *binary_status,
                                     cl_int *errcode_ret);

🌸 PARAMETERS 🌸

  • context — has to be a valid OpenCL context, like actually valid, no fake ones. 💅
  • device_list — a pointer to a list of devices that are in context. device_list must be a non-NULL value. The binaries get loaded for the devices in this list, that's the whole point.
  • num_devices — the number of devices listed in device_list.

The devices associated with the program object will be the list of devices specified by device_list. And the list of devices specified by device_list must be devices associated with context. like, they have to actually belong there. 🫶

  • lengths — an array of the size in bytes of the program binaries to be loaded, for the devices specified by device_list.
  • binaries — an array of pointers to program binaries to be loaded, for the devices specified by device_list. For each device given by device_list[i], the pointer to the program binary for that device is given by binaries[i], and the length of this corresponding binary is given by lengths[i]. lengths[i] cannot be zero and binaries[i] cannot be a NULL pointer. periodt.

The program binaries specified by binaries contain the bits that describe one of the following:

  • a program executable to be run on the device(s) associated with context.
  • a compiled program for device(s) associated with context.
  • a library of compiled programs for device(s) associated with context.

The program binary can consist of either or both of device-specific code and/or implementation-specific intermediate representation (IR) which will be converted to the device-specific code. it's giving ✨flexible✨.

  • binary_status — returns whether the program binary for each device specified in device_list was loaded successfully or not. It's an array of num_devices entries, and it returns CL_SUCCESS in binary_status[i] if binary was successfully loaded for the device specified by device_list[i]. Otherwise it returns CL_INVALID_VALUE if lengths[i] is zero or if binaries[i] is a NULL value, or CL_INVALID_BINARY in binary_status[i] if the program binary is not a valid binary for the specified device. If binary_status is NULL, it is ignored. (it's fine, it's just not paying attention 🙈)
  • errcode_ret — returns an appropriate error code. If errcode_ret is NULL, no error code is returned.

👑 NOTES 👑

OpenCL allows applications to create a program object using the program source or binary and build appropriate program executables. And bestie, this is so useful — it lets applications load program source and then compile and link to generate a program executable online on its first instance, for the appropriate OpenCL devices in the system. Those executables can now be queried and cached by the application. So future instances of the application launching will no longer need to compile and link the program executables. The cached executables can be read and loaded by the application, which can help significantly reduce the application initialization time. speed. it ate. 🔥

💀 ERRORS 💀

Returns a valid non-zero program object and errcode_ret is set to CL_SUCCESS if the program object is created successfully. Otherwise, it returns a NULL value with one of the following error values returned in errcode_ret:

  • CL_INVALID_CONTEXT if context is not a valid context.
  • CL_INVALID_VALUE if device_list is NULL or num_devices is zero;
  • CL_INVALID_DEVICE if OpenCL devices listed in device_list are not in the list of devices associated with context.
  • CL_INVALID_VALUE if or if lengths or binaries are NULL or if any entry in lengths[i] or binaries[i] is NULL.
  • CL_INVALID_BINARY if an invalid program binary was encountered for any device. binary_status will return specific status for each device.
  • CL_OUT_OF_RESOURCES if there is a failure to allocate resources required by the OpenCL implementation on the device.
  • CL_OUT_OF_HOST_MEMORY if there is a failure to allocate resources required by the OpenCL implementation on the host.

🎀 SPECIFICATION 🎀

OpenCL Specification[1]

🦋 SEE ALSO 🦋

clCreateProgramWithSource(3clc), clReleaseProgram(3clc), clRetainProgram(3clc), classDiagram(3clc)

💜 AUTHORS 💜

The Khronos Group

Copyright © 2007-2011 The Khronos Group Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and/or associated documentation files (the "Materials"), to deal in the Materials without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Materials, and to permit persons to whom the Materials are furnished to do so, subject to the condition that this copyright notice and permission notice shall be included in all copies or substantial portions of the Materials.

📚 NOTES 📚

  1. OpenCL Specification page 133, section 5.6.1 - Creating Program Objects

okay that's the whole page, bestie, you're officially certified in loading program binaries. slay 💅✨

this was brought to you by The Khronos Group, dated 01/14/2021, from the CLCREATEPROGRAMWITHB(3clc) page. mwah. 🫶💖
📦 where this page comes from