-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tidy up support for CL_MEM_OBJECT_IMAGE1D_BUFFER
#625
Comments
rjodinchr
added a commit
to rjodinchr/clvk
that referenced
this issue
Oct 30, 2023
also fix condition for CL_LUMINANCE and CL_INTENSITY (ref kpet#625)
rjodinchr
added a commit
to rjodinchr/clvk
that referenced
this issue
Oct 30, 2023
also fix condition for CL_LUMINANCE and CL_INTENSITY (ref kpet#625)
rjodinchr
added a commit
to rjodinchr/clvk
that referenced
this issue
Nov 13, 2023
also fix condition for CL_LUMINANCE and CL_INTENSITY (ref kpet#625)
rjodinchr
added a commit
to rjodinchr/clvk
that referenced
this issue
Nov 13, 2023
also fix condition for CL_LUMINANCE and CL_INTENSITY (ref kpet#625)
rjodinchr
added a commit
to rjodinchr/clvk
that referenced
this issue
Nov 13, 2023
also fix condition for CL_LUMINANCE and CL_INTENSITY (ref kpet#625)
kpet
pushed a commit
that referenced
this issue
Nov 13, 2023
also fix condition for CL_LUMINANCE and CL_INTENSITY (ref #625)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A few things to address after the initial PR:
CL_LUMINANCE
andCL_INTENSITY
formats. See add support for image1d_buffer #609 (comment)VK_FORMAT_FEATURE_2_STORAGE_WRITE_WITHOUT_FORMAT_BIT_KHR
for writable texel buffers. Probably depends on Add support for VK_KHR_format_feature_flags2 #497CL_DEVICE_MEM_BASE_ADDR_ALIGN
to take into account alignment requirements of texel buffers. See add support for image1d_buffer #609 (comment)The text was updated successfully, but these errors were encountered: