C Specification

To enqueue a command to copy a buffer object to an image object, call the function

// Provided by CL_VERSION_1_0
cl_int clEnqueueCopyBufferToImage(
    cl_command_queue command_queue,
    cl_mem src_buffer,
    cl_mem dst_image,
    size_t src_offset,
    const size_t* dst_origin,
    const size_t* region,
    cl_uint num_events_in_wait_list,
    const cl_event* event_wait_list,
    cl_event* event);

Parameters

  • command_queue must be a valid host command-queue. The OpenCL context associated with command_queue, src_buffer and dst_image must be the same.

  • src_buffer is a valid buffer object.

  • dst_image is a valid image object.

  • src_offset refers to the offset where to begin copying data from src_buffer.

  • dst_origin defines the (x, y, z) offset in pixels in the 1D, 2D or 3D image, the (x, y) offset and the image index in the 2D image array or the (x) offset and the image index in the 1D image array. If dst_image is a 2D image object, dst_origin[2] must be 0. If dst_image is a 1D image or 1D image buffer object, dst_origin[1] and dst_origin[2] must be 0. If dst_image is a 1D image array object, dst_origin[2] must be 0. If dst_image is a 1D image array object, dst_origin[1] describes the image index in the 1D image array. If dst_image is a 2D image array object, dst_origin[2] describes the image index in the 2D image array. If dst_image is a mipmapped image, the mip level to write is determined from dst_origin as described in Specifying Mipmap Levels to Image Operations

  • region defines the (width, height, depth) in pixels of the 1D, 2D or 3D rectangle, the (width, height) in pixels of the 2D rectangle and the number of images of a 2D image array or the (width) in pixels of the 1D rectangle and the number of images of a 1D image array. If dst_image is a 2D image object, region[2] must be 1. If dst_image is a 1D image or 1D image buffer object, region[1] and region[2] must be 1. If dst_image is a 1D image array object, region[2] must be 1. The values in region cannot be 0.

  • event_wait_list and num_events_in_wait_list specify events that need to complete before this particular command can be executed. If event_wait_list is NULL, then this particular command does not wait on any event to complete. If event_wait_list is NULL, num_events_in_wait_list must be 0. If event_wait_list is not NULL, the list of events pointed to by event_wait_list must be valid and num_events_in_wait_list must be greater than 0. The events specified in event_wait_list act as synchronization points. The context associated with events in event_wait_list and command_queue must be the same. The memory associated with event_wait_list can be reused or freed after the function returns.

  • event returns an event object that identifies this copy command and can be used to query or queue a wait for this command to complete. If event is NULL or the enqueue is unsuccessful, no event will be created and therefore it will not be possible to query the status of this command or to wait for this command to complete. If event_wait_list and event are not NULL, event must not refer to an element of the event_wait_list array.

Description

The size in bytes of the region to be copied from src_buffer referred to as src_cb is computed as width × height × depth × bytes/image element if dst_image is a 3D image object, is computed as width × height × bytes/image element if dst_image is a 2D image, is computed as width × height × arraysize × bytes/image element if dst_image is a 2D image array object, is computed as width × bytes/image element if dst_image is a 1D image or 1D image buffer object and is computed as width × arraysize × bytes/image element if dst_image is a 1D image array object.

The usage information which indicates whether the memory object can be read or written by a kernel and/or the host and is given by the cl_mem_flags argument value specified when src_buffer or dst_image is created is ignored by clEnqueueCopyBufferToImage.

clEnqueueCopyBufferToImage returns CL_SUCCESS if the function is executed successfully. Otherwise, it returns one of the following errors:

  • CL_INVALID_COMMAND_QUEUE

    • if command_queue is not a valid host command-queue

  • CL_INVALID_CONTEXT

    • if the context associated with command_queue and src_buffer are not the same

    • if the context associated with command_queue and dst_image are not the same

    • if the context associated with command_queue and events in event_wait_list are not the same

  • CL_INVALID_MEM_OBJECT

    • if src_buffer is not a valid buffer object

    • if dst_image is not a valid image object

    • if dst_image is a 1D image buffer object created from src_buffer

  • CL_INVALID_VALUE

    • if dst_origin is NULL

    • if region is NULL

    • if the region specified by src_offset and the computed src_cb is out of bounds of src_buffer

    • if the 1D, 2D or 3D rectangular region specified by dst_origin and region is out of bounds of dst_image

    • if values in dst_origin and region do not follow rules described in the argument description for dst_origin and region

  • CL_INVALID_MIP_LEVEL

    • if the cl_khr_mipmap_image extension is supported and the mip level specified in dst_origin is not a valid level for dst_image

  • CL_INVALID_EVENT_WAIT_LIST

    • if event_wait_list is NULL and num_events_in_wait_list is greater than zero

    • if event_wait_list is not NULL and num_events_in_wait_list is zero

    • if event objects in event_wait_list are not valid events

  • CL_MISALIGNED_SUB_BUFFER_OFFSET

    • if src_buffer is a sub-buffer object and the offset specified when the sub-buffer object was created is not aligned to the CL_DEVICE_MEM_BASE_ADDR_ALIGN value for the device associated with command_queue. This error code is missing before version 1.1.

  • CL_INVALID_IMAGE_SIZE

    • if the dimensions for dst_image, such as the image width or image height, are not supported by the device associated with command_queue

  • CL_IMAGE_FORMAT_NOT_SUPPORTED

    • if the format for dst_image, such as the image channel order or image channel data type, are not supported by the device associated with command_queue

  • CL_MEM_OBJECT_ALLOCATION_FAILURE

    • if there is a failure to allocate memory for the data store associated with src_buffer

    • if there is a failure to allocate memory for the data store associated with dst_image

  • CL_INVALID_OPERATION

    • if the device associated with command_queue does not support images (the query for CL_DEVICE_IMAGE_SUPPORT returns CL_FALSE)

    • if dst_image was created with CL_MEM_IMMUTABLE_EXT

  • 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

See Also

CL_VERSION_1_0, cl_command_queue, cl_event, cl_mem, cl_uint

Document Notes

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

Copyright 2014-2026 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0