e5fa7edfd6
Relaxed block layout relaxed the restrictions on vector alignment, allowing them to be aligned on scalar boundaries. Scalar block layout relaxes this further, allowing *any* member to be aligned on a scalar boundary. The requirement that a vector not improperly straddle a 16-byte boundary is also relaxed. I've also added a test showing that `std430` layout works with UBOs. I'm troubled by the dual meaning of the `Packed` extended decoration. In some instances (struct, `float[]`, and `vec2[]` members), it actually means the exact opposite, that the member needs extra padding. This is especially problematic for `vec2[]`, because now we need to distinguish the two cases by checking the array stride. I wonder if this should actually be split into two decorations. |
||
|---|---|---|
| .. | ||
| basic.multiview.nocompat.vk.frag | ||
| push-constant.vk.frag | ||
| scalar-block-layout-ubo-std430.vk.nocompat.invalid.frag | ||
| spec-constant.msl11.vk.frag | ||
| spec-constant.vk.frag | ||
| subgroups.nocompat.invalid.vk.msl21.frag | ||