Difference between revisions of "Interface Block (GLSL)"

From OpenGL.org
Jump to: navigation, search
m (Alfonse moved page GLSL Interface Blocks to GLSL Interface Block over redirect: Make everything singular, per Wikipedia standard)
(Separable program node.)
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Interface Blocks''' are ways to group uniforms, inputs, and outputs within [[GLSL]] shaders.
+
{{ infobox feature
 +
| core = 3.1
 +
| core_extension = [http://www.opengl.org/registry/specs/ARB/uniform_buffer_object.txt ARB_uniform_buffer_object], [http://www.opengl.org/registry/specs/ARB/shader_storage_buffer_object.txt ARB_shader_storage_buffer_object]
 +
}}
 +
 
 +
An ''Interface Block'' is a group of [[GLSL]] [[Type Qualifier (GLSL)#Storage qualifiers|input, output, uniform, or storage buffer variables]]. These blocks have special syntax and semantics that can be applied to them.
 +
 
 +
== Syntax ==
 +
 
 +
Interface blocks have different meanings in their various uses, but they have the same ''syntax'' regardless of how they are used. Uniform blocks are defined as follows:
 +
 
 +
<source lang=glsl>
 +
storage_qualifier block_name
 +
{
 +
  <define members here>
 +
} instance_name;
 +
</source>
 +
 
 +
This looks like a struct definition, but it is ''not''.
 +
 
 +
{{param|storage_qualifier}} can be one of {{code|in}}, {{code|out}}, {{code|uniform}}, or {{code|buffer}} (the latter requires GL 4.3). This defines what kind of interface block is being created.
 +
 
 +
{{param|block_name}} is the true name for the interface block. When the block is referenced in OpenGL code or otherwise talked about in most contexts, this is the name that is used.
 +
 
 +
{{param|instance_name}} is a GLSL name for one or more instances of the block named {{param|block_name}}. It is optional; if it is present, then all GLSL variables defined within the block must be scoped with the instance name. For example, this defines a uniform block:
 +
 
 +
<source lang=glsl>
 +
uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
} matrices;
 +
</source>
 +
 
 +
To access the {{code|projection}} member of this block, you must use {{code|matrices.projection}}.
 +
 
 +
If it were defined as follows:
 +
 
 +
<source lang=glsl>
 +
uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
};
 +
</source>
 +
 
 +
You simply use {{code|projection}} to refer to it. So the interface name acts as a namespace qualifier. ''At no time'' can you use {{code|MatrixBlock.projection}} in GLSL.
 +
 
 +
Because these names are defined globally, they can conflict with other names:
 +
 
 +
<source lang=glsl>
 +
uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
};
 +
 
 +
uniform vec3 modelview;  //Redefining variable. Compile error.
 +
</source>
 +
 
 +
The instance name can also define an array of blocks:
 +
 
 +
<source lang=glsl>
 +
uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
} matrices[3];
 +
</source>
 +
 
 +
This creates 3 separate interface blocks: {{code|matrices[0]}}, {{code|matrices[1]}}, and {{code|matrices[2]}}. These can have separate binding locations (see below), so they can come from different buffer objects.
 +
 
 +
For uniform and shader storage blocks, the array index must be a dynamically-uniform integral expression. For other kinds of blocks, they can be any arbitrary integral expression.
 +
 
 +
{{note|The interface name is only used by GLSL. OpenGL always uses the actual block name. Thus, the name of the above block is "{{code|MatrixBlock[1]}}".}}
 +
 
 +
Linking between shader stages allows multiple shaders to use the same block. Interface blocks match with each other based on the block name and the member field definitions. So the same block in different shader stages can have ''different'' instance names.
 +
 
 +
=== Valid types ===
 +
 
 +
Interface blocks cannot contain [[GLSL Types#Opaque types|opaque types]]. They also cannot contain nested structure definitions.
 +
 
 +
== Input and output ==
 +
 
 +
Input and output blocks are designed to compliment each other. Their primary utility is with [[Geometry Shader|geometry]] or [[Tessellation Shader|tessellation shaders]], as these shaders often work with aggregates of input/output values. Blocks make it easy to organize this data.
 +
 
 +
Interface blocks can ''only'' be used to aggregate data interfaces between shaders. Vertex shaders cannot declare an input interface block, and fragment shaders cannot declare an output interface block.
 +
 
 +
If the input interface uses a block, then the corresponding output must also be a block that uses the same block name and members (though not necessarily the same instance name). For example, a vertex shader can pass data to a geometry shader using these block definitions:
 +
 
 +
<source lang=glsl>
 +
//Vertex Shader
 +
out VertexData
 +
{
 +
  vec3 color;
 +
  vec2 texCoord;
 +
} outData;
 +
 
 +
//Geometry Shader
 +
in VertexData
 +
{
 +
  vec3 color;
 +
  vec2 texCoord;
 +
} inData[];
 +
</source>
 +
 
 +
Notice that the geometry shader block is defined as an array in the geometry shader. It also uses a different instance name. These work perfectly fine; the GS will receive a number of vertices based on the primitive type it is designed to take.
 +
 
 +
{{note| Input/output interface blocks don't use {{code|location}} names for interface matching. So in separable programs, interfaces must match directly.}}
 +
 
 +
The only types that are valid in input/output blocks are those which are valid as input/output variables.
 +
 
 +
== Buffer backed ==
 +
 
 +
Uniform blocks and shader storage blocks work in very similar ways, so this section will explain the features they have in common. Collectively, these are called "buffer-backed blocks" because the storage for their contents come from a [[Buffer Object]].
 +
 
 +
Note that shader storage blocks are a GL 4.3 feature, and thus are not available unless 4.3 or ARB_shader_storage_buffer_objects is defined.
 +
 
 +
=== Matrix storage order ===
 +
 
 +
Because the storage for these blocks comes from [[Buffer Object]]s, matrix ordering becomes important. Matrices can be stored in column or row-major ordering. Layout qualifiers are used to decide which is used on a per-variable basis.
 +
 
 +
Note that this ''does not'' change how GLSL works with them. GLSL matrices are ''always'' column-major. This specification only changes how GLSL fetches the data from the buffer.
 +
 
 +
Defaults can be set with this syntax:
 +
 
 +
layout(row_major) uniform;
 +
 
 +
From this point on, all matrices in uniform blocks are considered row-major. Shader storage blocks are not affected; they would need their own definition ({{code|layout(row_major) buffer;}}).
 +
 
 +
A particular block can have a default set as well:
 +
 
 +
<source lang=glsl>
 +
layout(row_major) uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
} matrices[3];
 +
</source>
 +
 
 +
All of the matrices are stored in row-major ordering.
 +
 
 +
Individual variables can be adjusted as well:
 +
 
 +
<source lang=glsl>
 +
layout(row_major) uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  layout(column_major) mat4 modelview;
 +
} matrices[3];
 +
</source>
 +
 
 +
{{code|MatrixBlock.projection}} is row-major, but {{code|MatrixBlock.modelview}} is column-major. The default is column-major.
 +
 
 +
=== Memory layout ===
 +
 
 +
The specific size of basic types used by members of buffer-backed blocks is defined by OpenGL. However, implementations are allowed some latitude when assigning padding ''between'' members, as well as reasonable freedom to optimize away unused members. How much freedom implementations are allowed for specific blocks can be changed.
 +
 
 +
There are four memory layout qualifiers: {{code|shared}}, {{code|packed}}, {{code|std140}}, and {{code|std420}}. Defaults can be set the same as for matrix ordering (eg: {{code|layout(packed) buffer;}} sets all shader storage buffer blocks to use {{code|packed}}). The default is {{code|shared}}.
 +
 
 +
The '''{{code|packed}}''' layout type means that the implementation determines everything about how the fields are laid out in the block. The OpenGL API can be used to query the layout for the members of a particular block. Each member of a block will have a particular byte offset, which you can use to determine how to upload its data. Also, members of a block can be optimized out if they are found by the implementation to not affect the result of the shader. Therefore, the active components of a block may not be all of the components it was defined with.
 +
 
 +
The last limitation makes it difficult to share buffers between different programs, even with identical block definitions. Therefore, the '''{{code|shared}}''' type exists. It works essentially the way {{code|packed}} does; you have to query offsets for each variable. However, {{code|shared}} has two major differences. First, it guarantees that all of the variables defined in the block are considered active. Second, it guarantees that the same buffer can be used between all programs that share this same block definition, so long as:
 +
 
 +
* The different programs use the ''exact same'' block definition (ignoring differences in variable names).
 +
* All members of the block use explicit sizes for arrays.
 +
 
 +
Because of these guarantees, buffer-backed blocks declared {{code|shared}} can be used with any program that defines a block with the same elements in the same order. This even works across different types of buffer-backed blocks. You can use a buffer as a uniform buffer at one point, then use it as a shader storage buffer in another. OpenGL guarantees that all of the offsets and alignments will match between two {{code|shared}} blocks that define the same members in the same order. In short, it allows the user to ''share'' buffers between multiple programs.
 +
 
 +
In both of the previous layout types, the user must query the offset for each variable of interest within the block. If you want to have a layout that is know without having to query this information, you may use '''{{code|std140}}''' or '''{{code|std430}}'''. The OpenGL Specification goes into great detail as to exactly how each element of these layout types are placed within a buffer. These layouts also has the same properties as '''shared''', in that all variables will be available, and that programs can share variables of this layout with each other (if the above conditions are adhered to).
 +
 
 +
{{code|std140}} layout will generally not use the most optimal packing in terms of size. This is the only real downside to using it.
 +
 
 +
Note that {{code|std430}} layout '''cannot''' be used with uniform blocks. It can only be used with storage buffer blocks. It offers greater packing and smaller alignment requirements than {{code|std140}}.
 +
 
 +
=== Block binding ===
 +
 
 +
Each uniform/shader storage block has a binding index. This index references one of a number of slots in the OpenGL context that say which buffer objects to use. When a buffer object is bound to the index reference by a block, then that block will get its data from that buffer.
 +
 
 +
If GL 4.2 or ARB_shading_language_420pack is defined, then the block binding indices can be set directly from the shader:
 +
 
 +
<source lang=glsl>
 +
layout(binding = 3) uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
};
 +
</source>
 +
 
 +
Uniform and shader storage blocks have a different set of indices. Uniform block binding indices refer to blocks bound to indices in the {{enum|GL_UNIFORM_BUFFER}} indexed target with {{apifunc|glBindBufferRange}}. Shader storage block binding indices refer to blocks bound to indices in the {{enum|GL_SHADER_STORAGE_BUFFER}} target.
 +
 
 +
For arrays of blocks, the binding syntax sequentially allocates indices. So this definition:
 +
 
 +
<source lang=glsl>
 +
layout(binding = 2) uniform MatrixBlock
 +
{
 +
  mat4 projection;
 +
  mat4 modelview;
 +
} matrices[4];
 +
</source>
 +
 
 +
There will be 4 separate blocks, which use the binding indices 2, 3, 4, and 5.
 +
 
 +
Block bindings can also be set manually from OpenGL. The function to do this depends on whether it is a uniform block or a shader storage block. See their individual sections.
 +
 
 +
Once a binding is assigned, the storage can be bound to the OpenGL context with {{apifunc|glBindBufferRange}} (or {{apifunc|glBindBufferBase}} for the whole buffer). Each type of buffer-backed block has its own target. Uniform blocks use {{enum|GL_UNIFORM_BUFFER}}, and shader storage blocks use {{enum|GL_SHADER_STORAGE_BUFFER}}.
 +
 
 +
=== Uniform blocks ===
 +
 
 +
Uniform blocks cannot use {{code|std430}} layout.
 +
 
 +
To set the block binding from OpenGL, you must first get the index for that uniform block. To do that, you may use one of these two functions:
 +
 
 +
GLuint {{apifunc|glGetProgramResourceIndex}}( GLuint {{param|program​}}, GLenum {{param|programInterface​}}, const char *{{param|name}} );
 +
GLuint {{apifunc|glGetUniformBlockIndex}}( GLuint {{param|program​}}, const char *{{param|name​}} );
 +
 
 +
The first function is only available in GL version 4.3 or if ARB_program_interface_query is available. The latter is always available. If you use {{apifunc|glGetProgramResourceIndex}}, the {{param|programInterface​}} parameter should be {{enum|GL_UNIFORM_BLOCK}}.
 +
 
 +
If {{param|name}} specifies a block that is inactive, or specifies a block that isn't defined in {{param|program}}, then {{enum|GL_INVALID_INDEX}} is returned.
 +
 
 +
Once the index is retrieved, it can be used to set the buffer binding with this function:
 +
 
 +
void {{apifunc|glUniformBlockBinding}}( GLuint {{param|program​}}, GLuint {{param|uniformBlockIndex​}}, GLuint {{param|uniformBlockBinding​}} );
 +
 
 +
This causes the uniform block specified by {{param|uniformBlockIndex​}} in {{param|program​}} to use the uniform buffer binding location {{param|uniformBlockBinding​}}.
 +
 
 +
There are only {{enum|GL_MAX_UNIFORM_BUFFER_BINDINGS}} binding locations available. So {{param|uniformBlockBinding​}} must be less than this value.
 +
 
 +
=== Shader storage blocks ===
 +
 
 +
If the last member variable of a shader storage block is declared with an indeterminate array length (using {{code|[]}}), then the size of this array is determined at the time the shader is executed. The size is basically the rest of the buffer object range that was attached to that binding point.
 +
 
 +
For example, consider the following:
 +
 
 +
<source lang=glsl>
 +
layout(std430, binding = 2) buffer MyBuffer
 +
{
 +
  mat4 matrix;
 +
  float lotsOfFloats[];
 +
};
 +
</source>
 +
 
 +
The number of {{code|float}} variables in {{code|lotsOfFloats}} depends on the size of the buffer range that is attached to the binding point. {{code|matrix}} will be 64 bytes in size, so the number of elements in {{code|lotsOfFloats}} will be (size of the bound range minus 64) / 4. Thus, if we bind with this:
 +
 
 +
{{apifunc|glBindBufferRange}}(GL_SHADER_STORAGE_BUFFER, 2, buffer, 0, 128);
 +
 
 +
There will be (128 - 64) / 4, or 16 elements in {{code|lotsOfFloats}}. Thus, {{code|lotsOfFloats.length()}} will return 16. It will return a different value depending on the size of the bound range.
 +
 
 +
==== Manual block binding ====
 +
 
 +
As with uniform blocks, you must get the index to the shader storage block in order to manually bind it. There is only one function to do this:
 +
 
 +
GLuint {{apifunc|glGetProgramResourceIndex}}( GLuint {{param|program​}}, GLenum {{param|programInterface​}}, const char *{{param|name}} );
 +
 
 +
In this case, {{param|programInterface}} should be {{enum|GL_SHADER_STORAGE_BLOCK​}}.
 +
 
 +
If {{param|name}} specifies a block that is inactive, or specifies a block that isn't defined in {{param|program}}, then {{enum|GL_INVALID_INDEX}} is returned.
 +
 
 +
Once the index is retrieved, it can be used to set the buffer binding with this function:
 +
 
 +
void {{apifunc|glShaderStorageBlockBinding}}( GLuint {{param|program​}}, GLuint {{param|storageBlockIndex​}}, GLuint {{param|storageBlockBinding​}} )
 +
 
 +
This causes the shader storage block specified by {{param|storageBlockIndex​}} in {{param|program​}} to use the shader storage buffer binding location {{param|storageBlockBinding​}}.
 +
 
 +
There are only {{enum|GL_MAX_SHADER_STORAGE_BUFFER_BINDINGS}} binding locations available. So {{param|storageBlockBinding​}} must be less than this value.
  
{{stub}}
 
  
 
[[Category:OpenGL Shading Language]]
 
[[Category:OpenGL Shading Language]]

Revision as of 23:34, 22 October 2012

Interface Block (GLSL)
Core in version 4.5
Core since version 3.1
Core ARB extension ARB_uniform_buffer_object, ARB_shader_storage_buffer_object

An Interface Block is a group of GLSL input, output, uniform, or storage buffer variables. These blocks have special syntax and semantics that can be applied to them.

Syntax

Interface blocks have different meanings in their various uses, but they have the same syntax regardless of how they are used. Uniform blocks are defined as follows:

storage_qualifier block_name
{
  <define members here>
} instance_name;

This looks like a struct definition, but it is not.

storage_qualifier​ can be one of in​, out​, uniform​, or buffer​ (the latter requires GL 4.3). This defines what kind of interface block is being created.

block_name​ is the true name for the interface block. When the block is referenced in OpenGL code or otherwise talked about in most contexts, this is the name that is used.

instance_name​ is a GLSL name for one or more instances of the block named block_name​. It is optional; if it is present, then all GLSL variables defined within the block must be scoped with the instance name. For example, this defines a uniform block:

uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
} matrices;

To access the projection​ member of this block, you must use matrices.projection​.

If it were defined as follows:

uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
};

You simply use projection​ to refer to it. So the interface name acts as a namespace qualifier. At no time can you use MatrixBlock.projection​ in GLSL.

Because these names are defined globally, they can conflict with other names:

uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
};
 
uniform vec3 modelview;  //Redefining variable. Compile error.

The instance name can also define an array of blocks:

uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
} matrices[3];

This creates 3 separate interface blocks: matrices[0]​, matrices[1]​, and matrices[2]​. These can have separate binding locations (see below), so they can come from different buffer objects.

For uniform and shader storage blocks, the array index must be a dynamically-uniform integral expression. For other kinds of blocks, they can be any arbitrary integral expression.

Note: The interface name is only used by GLSL. OpenGL always uses the actual block name. Thus, the name of the above block is "MatrixBlock[1]​".

Linking between shader stages allows multiple shaders to use the same block. Interface blocks match with each other based on the block name and the member field definitions. So the same block in different shader stages can have different instance names.

Valid types

Interface blocks cannot contain opaque types. They also cannot contain nested structure definitions.

Input and output

Input and output blocks are designed to compliment each other. Their primary utility is with geometry or tessellation shaders, as these shaders often work with aggregates of input/output values. Blocks make it easy to organize this data.

Interface blocks can only be used to aggregate data interfaces between shaders. Vertex shaders cannot declare an input interface block, and fragment shaders cannot declare an output interface block.

If the input interface uses a block, then the corresponding output must also be a block that uses the same block name and members (though not necessarily the same instance name). For example, a vertex shader can pass data to a geometry shader using these block definitions:

//Vertex Shader
out VertexData
{
  vec3 color;
  vec2 texCoord;
} outData;
 
//Geometry Shader
in VertexData
{
  vec3 color;
  vec2 texCoord;
} inData[];

Notice that the geometry shader block is defined as an array in the geometry shader. It also uses a different instance name. These work perfectly fine; the GS will receive a number of vertices based on the primitive type it is designed to take.

Note: Input/output interface blocks don't use location​ names for interface matching. So in separable programs, interfaces must match directly.

The only types that are valid in input/output blocks are those which are valid as input/output variables.

Buffer backed

Uniform blocks and shader storage blocks work in very similar ways, so this section will explain the features they have in common. Collectively, these are called "buffer-backed blocks" because the storage for their contents come from a Buffer Object.

Note that shader storage blocks are a GL 4.3 feature, and thus are not available unless 4.3 or ARB_shader_storage_buffer_objects is defined.

Matrix storage order

Because the storage for these blocks comes from Buffer Objects, matrix ordering becomes important. Matrices can be stored in column or row-major ordering. Layout qualifiers are used to decide which is used on a per-variable basis.

Note that this does not change how GLSL works with them. GLSL matrices are always column-major. This specification only changes how GLSL fetches the data from the buffer.

Defaults can be set with this syntax:

layout(row_major) uniform;

From this point on, all matrices in uniform blocks are considered row-major. Shader storage blocks are not affected; they would need their own definition (layout(row_major) buffer;​).

A particular block can have a default set as well:

layout(row_major) uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
} matrices[3];

All of the matrices are stored in row-major ordering.

Individual variables can be adjusted as well:

layout(row_major) uniform MatrixBlock
{
  mat4 projection;
  layout(column_major) mat4 modelview;
} matrices[3];

MatrixBlock.projection​ is row-major, but MatrixBlock.modelview​ is column-major. The default is column-major.

Memory layout

The specific size of basic types used by members of buffer-backed blocks is defined by OpenGL. However, implementations are allowed some latitude when assigning padding between members, as well as reasonable freedom to optimize away unused members. How much freedom implementations are allowed for specific blocks can be changed.

There are four memory layout qualifiers: shared​, packed​, std140​, and std420​. Defaults can be set the same as for matrix ordering (eg: layout(packed) buffer;​ sets all shader storage buffer blocks to use packed​). The default is shared​.

The packed​ layout type means that the implementation determines everything about how the fields are laid out in the block. The OpenGL API can be used to query the layout for the members of a particular block. Each member of a block will have a particular byte offset, which you can use to determine how to upload its data. Also, members of a block can be optimized out if they are found by the implementation to not affect the result of the shader. Therefore, the active components of a block may not be all of the components it was defined with.

The last limitation makes it difficult to share buffers between different programs, even with identical block definitions. Therefore, the shared​ type exists. It works essentially the way packed​ does; you have to query offsets for each variable. However, shared​ has two major differences. First, it guarantees that all of the variables defined in the block are considered active. Second, it guarantees that the same buffer can be used between all programs that share this same block definition, so long as:

  • The different programs use the exact same block definition (ignoring differences in variable names).
  • All members of the block use explicit sizes for arrays.

Because of these guarantees, buffer-backed blocks declared shared​ can be used with any program that defines a block with the same elements in the same order. This even works across different types of buffer-backed blocks. You can use a buffer as a uniform buffer at one point, then use it as a shader storage buffer in another. OpenGL guarantees that all of the offsets and alignments will match between two shared​ blocks that define the same members in the same order. In short, it allows the user to share buffers between multiple programs.

In both of the previous layout types, the user must query the offset for each variable of interest within the block. If you want to have a layout that is know without having to query this information, you may use std140​ or std430​. The OpenGL Specification goes into great detail as to exactly how each element of these layout types are placed within a buffer. These layouts also has the same properties as shared, in that all variables will be available, and that programs can share variables of this layout with each other (if the above conditions are adhered to).

std140​ layout will generally not use the most optimal packing in terms of size. This is the only real downside to using it.

Note that std430​ layout cannot be used with uniform blocks. It can only be used with storage buffer blocks. It offers greater packing and smaller alignment requirements than std140​.

Block binding

Each uniform/shader storage block has a binding index. This index references one of a number of slots in the OpenGL context that say which buffer objects to use. When a buffer object is bound to the index reference by a block, then that block will get its data from that buffer.

If GL 4.2 or ARB_shading_language_420pack is defined, then the block binding indices can be set directly from the shader:

layout(binding = 3) uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
};

Uniform and shader storage blocks have a different set of indices. Uniform block binding indices refer to blocks bound to indices in the GL_UNIFORM_BUFFER indexed target with glBindBufferRange. Shader storage block binding indices refer to blocks bound to indices in the GL_SHADER_STORAGE_BUFFER target.

For arrays of blocks, the binding syntax sequentially allocates indices. So this definition:

layout(binding = 2) uniform MatrixBlock
{
  mat4 projection;
  mat4 modelview;
} matrices[4];

There will be 4 separate blocks, which use the binding indices 2, 3, 4, and 5.

Block bindings can also be set manually from OpenGL. The function to do this depends on whether it is a uniform block or a shader storage block. See their individual sections.

Once a binding is assigned, the storage can be bound to the OpenGL context with glBindBufferRange (or glBindBufferBase for the whole buffer). Each type of buffer-backed block has its own target. Uniform blocks use GL_UNIFORM_BUFFER, and shader storage blocks use GL_SHADER_STORAGE_BUFFER.

Uniform blocks

Uniform blocks cannot use std430​ layout.

To set the block binding from OpenGL, you must first get the index for that uniform block. To do that, you may use one of these two functions:

GLuint glGetProgramResourceIndex( GLuint program​​, GLenum programInterface​​, const char *name​ );
GLuint glGetUniformBlockIndex( GLuint program​​, const char *name​​ );

The first function is only available in GL version 4.3 or if ARB_program_interface_query is available. The latter is always available. If you use glGetProgramResourceIndex, the programInterface​​ parameter should be GL_UNIFORM_BLOCK.

If name​ specifies a block that is inactive, or specifies a block that isn't defined in program​, then GL_INVALID_INDEX is returned.

Once the index is retrieved, it can be used to set the buffer binding with this function:

void glUniformBlockBinding( GLuint program​​, GLuint uniformBlockIndex​​, GLuint uniformBlockBinding​​ );

This causes the uniform block specified by uniformBlockIndex​​ in program​​ to use the uniform buffer binding location uniformBlockBinding​​.

There are only GL_MAX_UNIFORM_BUFFER_BINDINGS binding locations available. So uniformBlockBinding​​ must be less than this value.

Shader storage blocks

If the last member variable of a shader storage block is declared with an indeterminate array length (using []​), then the size of this array is determined at the time the shader is executed. The size is basically the rest of the buffer object range that was attached to that binding point.

For example, consider the following:

layout(std430, binding = 2) buffer MyBuffer
{
  mat4 matrix;
  float lotsOfFloats[];
};

The number of float​ variables in lotsOfFloats​ depends on the size of the buffer range that is attached to the binding point. matrix​ will be 64 bytes in size, so the number of elements in lotsOfFloats​ will be (size of the bound range minus 64) / 4. Thus, if we bind with this:

glBindBufferRange(GL_SHADER_STORAGE_BUFFER, 2, buffer, 0, 128);

There will be (128 - 64) / 4, or 16 elements in lotsOfFloats​. Thus, lotsOfFloats.length()​ will return 16. It will return a different value depending on the size of the bound range.

Manual block binding

As with uniform blocks, you must get the index to the shader storage block in order to manually bind it. There is only one function to do this:

GLuint glGetProgramResourceIndex( GLuint program​​, GLenum programInterface​​, const char *name​ );

In this case, programInterface​ should be GL_SHADER_STORAGE_BLOCK​.

If name​ specifies a block that is inactive, or specifies a block that isn't defined in program​, then GL_INVALID_INDEX is returned.

Once the index is retrieved, it can be used to set the buffer binding with this function:

void glShaderStorageBlockBinding( GLuint program​​, GLuint storageBlockIndex​​, GLuint storageBlockBinding​​ )

This causes the shader storage block specified by storageBlockIndex​​ in program​​ to use the shader storage buffer binding location storageBlockBinding​​.

There are only GL_MAX_SHADER_STORAGE_BUFFER_BINDINGS binding locations available. So storageBlockBinding​​ must be less than this value.