SDL_CreateGPUComputePipeline(3)

✨ NAME ✨

SDL_CreateGPUComputePipeline — bestie, this is the one that creates a pipeline object so you can do a whole compute workflow 💅✨

It lives in the SDL3 FUNCTIONS family, and the manual page you're reading is SDL_CreateGPUComputePipeline(3). Hiii, welcome, let's get into it 🫶

---

🌸 SYNOPSIS 🌸

#include <SDL3/SDL_gpu.h>

SDL_GPUComputePipeline * SDL_CreateGPUComputePipeline(
    SDL_GPUDevice *device,
    const SDL_GPUComputePipelineCreateInfo *createinfo);

Two args, one pointer back. Iconic honestly.

---

🦋 DESCRIPTION 🦋

Okay so here's the tea ☕ — your shader resource bindings have to be authored in a particular order, and that order depends on which shader format you're rolling with. This is not a suggestion, it's the vibe check your shaders must pass. 🔥

🌈 For SPIR-V shaders

Use these resource sets, in this exact order:

• 0: Sampled textures, followed by read-only storage textures, followed by read-only storage buffers
• 1: Read-write storage textures, followed by read-write storage buffers
• 2: Uniform buffers

🎀 For DXBC and DXIL shaders

Use this register order:

• (t[n], space0): Sampled textures, followed by read-only storage textures, followed by read-only storage buffers
• (u[n], space1): Read-write storage textures, followed by read-write storage buffers
• (b[n], space2): Uniform buffers

💜 For MSL/metallib

Use this order:

• [[buffer]]: Uniform buffers, followed by read-only storage buffers, followed by read-write storage buffers
• [[texture]]: Sampled textures, followed by read-only storage textures, followed by read-write storage textures

---

There are optional properties you can hand over through props 🎁 — and these are the ones that are supported:

• SDL_PROP_GPU_COMPUTEPIPELINE_CREATE_NAME_STRING: a name that can be displayed in debugging tools.

That's it, that's the list. A cute lil name for your pipeline so the debugger doesn't just call it "thing #4" 😭

---

💖 FUNCTION PARAMETERS 💖

• device — a GPU Context. Your whole GPU situation lives here, bestie.
• createinfo — a struct describing the state of the compute pipeline to create. This is where you say what you want it to be, no cap.

---

👑 RETURN VALUE 👑

Returns a compute pipeline object on success 💅, or NULL on failure — and if you get that NULL, call SDL_GetError() for more information, because she WILL tell you what went wrong. Go read it, fr fr. 🫶

---

⭐ AVAILABILITY ⭐

This function is available since SDL 3.2.0. If you're on anything older, it's giving... not available, sorry babe. 🙈

---

🔥 SEE ALSO 🔥

• SDL_BindGPUComputePipeline(3)
• SDL_ReleaseGPUComputePipeline(3)

The whole trilogy — create it, bind it, release it. Main character energy all around. ✨

---

Simple Directmedia Layer wrote this whole thing, and the version on this page is SDL 3.4.18 💖 That's the source and the version, folded into one cute lil sign-off. Now go make that compute pipeline, bestie, you got this 🌸🦋💅