d92de00cc1
This is a fairly fundamental change on how IDs are handled.
It serves many purposes:
- Improve performance. We only need to iterate over IDs which are
relevant at any one time.
- Makes sure we iterate through IDs in SPIR-V module declaration order
rather than ID space. IDs don't have to be monotonically increasing,
which was an assumption SPIRV-Cross used to have. It has apparently
never been a problem until now.
- Support LUTs of structs. We do this by interleaving declaration of
constants and struct types in SPIR-V module order.
To support this, the ParsedIR interface needed to change slightly.
Before setting any ID with variant_set<T> we let ParsedIR know
that an ID with a specific type has been added. The surface for change
should be minimal.
ParsedIR will maintain a per-type list of IDs which the cross-compiler
will need to consider for later.
Instead of looping over ir.ids[] (which can be extremely large), we loop
over types now, using:
ir.for_each_typed_id<SPIRVariable>([&](uint32_t id, SPIRVariable &var) {
handle_variable(var);
});
Now we make sure that we're never looking at irrelevant types.
30 lines
664 B
GLSL
30 lines
664 B
GLSL
#version 310 es
|
|
precision mediump float;
|
|
precision highp int;
|
|
|
|
struct Foobar
|
|
{
|
|
float a;
|
|
float b;
|
|
};
|
|
|
|
const vec4 _37[3] = vec4[](vec4(1.0), vec4(2.0), vec4(3.0));
|
|
const vec4 _55[2][2] = vec4[][](vec4[](vec4(1.0), vec4(2.0)), vec4[](vec4(8.0), vec4(10.0)));
|
|
const Foobar _75[2] = Foobar[](Foobar(10.0, 40.0), Foobar(90.0, 70.0));
|
|
|
|
layout(location = 0) out vec4 FragColor;
|
|
layout(location = 0) flat in mediump int index;
|
|
|
|
vec4 resolve(Foobar f)
|
|
{
|
|
return vec4(f.a + f.b);
|
|
}
|
|
|
|
void main()
|
|
{
|
|
Foobar param = Foobar(10.0, 20.0);
|
|
Foobar param_1 = _75[index];
|
|
FragColor = ((_37[index] + _55[index][index + 1]) + resolve(param)) + resolve(param_1);
|
|
}
|
|
|