Greetings,
I'm currently playing with OpenGL ES 3.0 and I'm wondering if Mali (>= T6xx) drivers can perform interesting optimisations based on the chosen layout qualifier applied to Interface Blocks ? (shared, packed, std140, row_major, column_major)
The fact that Std140 avoids pinging the OpenGL implementation, about the data layout, makes me wonder if there's any reason to choose another layout qualifier.
Just one last question !
When searching for OpenGL ES 3.1 on the web, I found slides from the ARM Mali team presenting the new ES 3.1 features. Between these features there is :
As I understand it, I can define a specific ID for uniforms and, then, just reference the static ID on the API (C/C++) side like this :
glUniform*(myy_program_uniform_id, ...)
The question is : does it have the same impact as forcing layouts ?
The explicit locations set in the shader define the bind point name used for each symbol; without this explicit setting they can be set arbitrarily by the driver and different drivers will do different things with them. All the explicit location support means is that if you set the location in the shader you no longer need to call glGetUniformLocation at run-time, you can just use the pre-defined location value set in the shader source code.
glGetUniformLocation
HTH, Pete