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.
39 lines
767 B
Plaintext
39 lines
767 B
Plaintext
#version 310 es
|
|
layout(local_size_x = 2, local_size_y = 1, local_size_z = 1) in;
|
|
|
|
struct Data
|
|
{
|
|
float a;
|
|
float b;
|
|
};
|
|
|
|
#ifndef SPIRV_CROSS_CONSTANT_ID_0
|
|
#define SPIRV_CROSS_CONSTANT_ID_0 4.0
|
|
#endif
|
|
const float X = SPIRV_CROSS_CONSTANT_ID_0;
|
|
|
|
layout(binding = 0, std430) buffer SSBO
|
|
{
|
|
Data outdata[];
|
|
} _53;
|
|
|
|
Data data[2];
|
|
Data data2[2];
|
|
|
|
Data combine(Data a, Data b)
|
|
{
|
|
return Data(a.a + b.a, a.b + b.b);
|
|
}
|
|
|
|
void main()
|
|
{
|
|
data = Data[](Data(1.0, 2.0), Data(3.0, 4.0));
|
|
data2 = Data[](Data(X, 2.0), Data(3.0, 5.0));
|
|
Data param = data[gl_LocalInvocationID.x];
|
|
Data param_1 = data2[gl_LocalInvocationID.x];
|
|
Data _73 = combine(param, param_1);
|
|
_53.outdata[gl_WorkGroupID.x].a = _73.a;
|
|
_53.outdata[gl_WorkGroupID.x].b = _73.b;
|
|
}
|
|
|