CL_KHR_D3D10_SHARING(3clc)

💖 CL_KHR_D3D10_SHARING 💖

okay bestie, welcome to the OpenCL Manual page for cl_khr_d3d10_sharing — yes that's a mouthful, yes it's iconic, let's go 🫶

---

✨ NAME ✨

cl_khr_d3d10_sharing — the extension that makes OpenCL and Direct3D 10 actually talk to each other. friendship bracelet energy fr fr 🎀

#pragma OPENCL EXTENSION
cl_khr_d3d10_sharing : enable

---

🌸 DESCRIPTION 🌸

so the whole goal here? providing interoperability between OpenCL and Direct3D 10. that's the mission, that's the vibe. 💅

it's designed to work analogously to cl_khr_gl_sharing(3clc) as defined in sections 9.7 and 9.8. no cap.

and listen — if an implementation supports this extension, the string "cl_khr_d3d10_sharing" will show up in the CL_PLATFORM_EXTENSIONS or CL_DEVICE_EXTENSIONS string described in the table of allowed values for param_name for clGetDeviceInfo(3clc). that's your vibe check, that's how you know it's real 👑

as currently proposed, the interfaces for this extension would be provided in cl_d3d10.h. noted. 🍓

if the cl_khr_d3d10_sharing extension is supported, then these functions get enabled:

• clGetDeviceIDsFromD3D10KHR(3clc)
• clCreateFromD3D10BufferKHR(3clc)
• clCreateFromD3D10Texture2DKHR(3clc)
• clCreateFromD3D10Texture3DKHR(3clc)
• clEnqueueAcquireD3D10ObjectsKHR(3clc)
• clEnqueueReleaseD3D10ObjectsKHR(3clc)

so here's the tea, and it's genuinely good tea ☕✨

the OpenCL functions enabled by the cl_khr_d3d10_sharing extension let applications use Direct3D 10 resources as OpenCL memory objects. that means efficient sharing of data between OpenCL and Direct3D 10. main character behavior.

the OpenCL API may be used to execute kernels that read and/or write memory objects that are also Direct3D 10 resources. yes literally both. 😭

• an OpenCL image object may be created from a Direct3D 10 texture resource.
• an OpenCL buffer object may be created from a Direct3D 10 buffer resource.

⚠️ important, don't skip this one bestie: OpenCL memory objects may be created from Direct3D 10 objects if and only if the OpenCL context has been created from a Direct3D 10 device. if and only if. not "usually", not "when you feel like it". periodt. 💀

---

📜 SPECIFICATION 📜

OpenCL Specification[1]

---

👀 SEE ALSO 👀

EXTENSION(3clc), clGetDeviceIDsFromD3D10KHR(3clc), clCreateFromD3D10BufferKHR(3clc), clCreateFromD3D10Texture2DKHR(3clc), clCreateFromD3D10Texture3DKHR(3clc), clEnqueueAcquireD3D10ObjectsKHR(3clc), clEnqueueReleaseD3D10ObjectsKHR(3clc)

---

🧚 AUTHORS 🧚

The Khronos Group

---

⭐ COPYRIGHT ⭐

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 66, section 9.9 - Sharing Memory Objects with Direct3D 10

---

and that's the whole page bestie, we ate and left no crumbs 🍽️✨ this little legend is brought to you by The Khronos Group, dated 01/14/2021 — mwah, sending you off with the biggest kiss, go make some OpenCL ↔ Direct3D 10 magic happen 💖🦋🌈