8

I've been using Vulkan for a while but I just now learned about specialization constants. The specification says:

Specialization constants are useful to allow a compute shader to have its local workgroup size changed at runtime by the user, for example.

Neat! I want to do almost exactly that, and I would like to use such varying constants for other purposes as well. But the examples of specialization constants given in the Vulkan specification (version 1.0.34 at the moment) all appear to be in SPIR-V, not GLSL, and my shaders are all written in GLSL. So I think I probably can't use this nice feature. :(

Am I right? Or is there a way to use specialization constants via GLSL, either as workgroup size constants, or as arbitrary constant variable values, or in some other fashion?

mjwach
  • 1,174
  • 2
  • 9
  • 25

1 Answers1

20

Sure, specialization constants can be used with GLSL in Vulkan as per GL_KHR_Vulkan.

It's a special layout qualifier, so your GLSL specialization constants will look like this:

layout (constant_id = 0) const int SSAO_KERNEL_SIZE = 64;

Values for those constants are then specified upon pipeline creation using the pSpecializationInfo member of the shader stage create info used in the pipeline create info.

This also works fine for e.g. compute shader workgroup sizes.

Andreas Flöjt
  • 349
  • 4
  • 10
Sascha Willems
  • 5,280
  • 1
  • 14
  • 21
  • Hmm, now I see documentation for it! https://www.khronos.org/registry/vulkan/specs/misc/GL_KHR_vulkan_glsl.txt ...But that document, if I understand right, is saying the syntax for workgroup sizes is different from what you say here. At any rate my question is answered though, thanks! – mjwach Nov 24 '16 at 04:29