READ_IMAGEH3D(3clc)

πŸ“¦
version 1.0~svn33624 Β· 3 versions
, in ubuntu jammy, ubuntu noble

πŸ’– READ_IMAGEH (3D) πŸ’–

okay bestie, welcome to read_imageh (3D) from the OpenCL Manual β€” yes, the manual name is literally right there, we're being fancy today ✨


🌸 NAME 🌸

read_imageh_(3D) β€” do an element lookup in the 3D image object, and get half floating-point values back. no cap, that's the whole gig πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

half4 read_imageh(image3d_t image, sampler_t sampler, int4 coord);

half4 read_imageh(image3d_t image, sampler_t sampler, float4 coord);

half4 read_imageh(image3d_t image, int4 coord);

three whole flavors, pick your fighter πŸ’…


✨ DESCRIPTION ✨

so you take the coordinate (coord.x, coord.y, coord.z) and you use it to do an element lookup in the 3D image object specified by image. and coord.w? ignored. not invited. blocked. 🚫

the samplerless read image functions behave exactly as the corresponding read image functions that take integer coordinates and a sampler with:

  • filter mode set to CLK_FILTER_NEAREST
  • normalized coordinates set to CLK_NORMALIZED_COORDS_FALSE
  • addressing mode set to CLK_ADDRESS_NONE

read_imageh returns half floating-point values in the range [0.0... 1.0] for image objects created with image_channel_data_type set to one of the predefined packed formats or CL_UNORM_INT8 or CL_UNORM_INT16. 🫢

read_imageh returns half floating-point values in the range [-1.0... 1.0] for image objects created with image_channel_data_type set to CL_SNORM_INT8, or CL_SNORM_INT16. 😌

read_imageh returns half floating-point values for image objects created with image_channel_data_type set to CL_HALF_FLOAT. 🧚

⚠️ okay listen up bestie, this part is IMPORTANT: the read_imageh calls that take integer coordinates must use a sampler with filter mode set to CLK_FILTER_NEAREST, normalized coordinates set to CLK_NORMALIZED_COORDS_FALSE and addressing mode set to CLK_ADDRESS_CLAMP_TO_EDGE, CLK_ADDRESS_CLAMP or CLK_ADDRESS_NONE; otherwise the values returned are undefined. undefined!! like, no promises, we don't know her πŸ’€

values returned by read_imageh for image objects with image_channel_data_type values not specified in the description above are undefined too. yeah. πŸ™ˆ


πŸ’œ NOTES πŸ’œ

general information about the read_image* functions follows. buckle up, it's lore time πŸ“–

the built-in functions defined in this section can only be used with image memory objects. an image memory object can be accessed by specific function calls that read from and/or write to specific locations in the image. ✨

image memory objects that are being read by a kernel should be declared with the accessQualifiers(3clc) qualifier. write_image calls to image memory objects declared with the accessQualifiers(3clc) qualifier will generate a compilation error. image memory objects that are being written to by a kernel should be declared with the accessQualifiers(3clc) qualifier. read_image calls to image memory objects declared with the accessQualifiers(3clc) qualifier will generate a compilation error. and read_image and write_image calls to the same image memory object in a kernel are not supported. pick a lane, bestie 😀

the read_image calls return a four component floating-point, integer or unsigned integer color value. the color values returned by read_image are identified as x, y, z, w where x refers to the red component, y refers to the green component, z refers to the blue component and w refers to the alpha component. 🌈

πŸŽ€ the channel mapping chart (but make it a list) πŸŽ€

the following describes the mapping of the number of channels of an image element to the appropriate components in the float4, int4 or uint4 vector data type for the color values returned by read_image{f|i|ui} or supplied to write_image{f|i|ui}. the unmapped components will be set to 0.0 for red, green and blue channels and will be set to 1.0 for the alpha channel. πŸ’…

  • Channel Order: CL_R, CL_Rx β†’ float4, int4 or uint4 components of channel data: (r, 0.0, 0.0, 1.0)
  • Channel Order: CL_A β†’ float4, int4 or uint4 components of channel data: (0.0, 0.0, 0.0, a)
  • Channel Order: CL_RG, CL_RGx β†’ float4, int4 or uint4 components of channel data: (r, g, 0.0, 1.0)
  • Channel Order: CL_RA β†’ float4, int4 or uint4 components of channel data: (r, 0.0, 0.0, a)
  • Channel Order: CL_RGB, CL_RGBx β†’ float4, int4 or uint4 components of channel data: (r, g, b, 1.0)
  • Channel Order: CL_RGBA, CL_BGRA, CL_ARGB β†’ float4, int4 or uint4 components of channel data: (r, g, b, a)
  • Channel Order: CL_INTENSITY β†’ float4, int4 or uint4 components of channel data: (I, I, I, I)
  • Channel Order: CL_LUMINANCE β†’ float4, int4 or uint4 components of channel data: (L, L, L, 1.0)

a kernel that uses a sampler with the CL_ADDRESS_CLAMP addressing mode with multiple images may result in additional samplers being used internally by an implementation. if the same sampler is used with multiple images called via read_image{f|i|ui}, then it is possible that an implementation may need to allocate an additional sampler to handle the different border color values that may be needed depending on the image formats being used. these implementation allocated samplers will count against the maximum sampler values supported by the device and given by CL_DEVICE_MAX_SAMPLERS. enqueuing a kernel that requires more samplers than the implementation can support will result in a CL_OUT_OF_RESOURCES error being returned. 😭


⭐ SPECIFICATION ⭐

OpenCL Specification[1] πŸ“š


🫢 SEE ALSO 🫢


πŸ‘‘ 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 27, section 9.5.8 - Image Read and Write Functions (half)

✨ okay that's the whole page bestie, you ate πŸ’… courtesy of The Khronos Group, dated 01/14/2021 β€” go read some images, main character πŸ¦‹πŸ’–
πŸ“¦ where this page comes from