4b99fdd5d0
Two varyings (vertex outputs/fragment inputs) might have the same location but be in different components--e.g. the compiler may have packed what were two different varyings into a single varying vector. Giving both varyings the same `[[user]]` attribute won't work--it may yield unexpected results, or flat out fail to link. We could eventually pack such varyings into a single vector, but that would require us to handle the case where the varyings are different types--e.g. a `float` and a `uint` packed into the same vector. For now, it seems most prudent to give them unique `[[user]]` locations and let Apple's compiler work out the best way to pack them. |
||
---|---|---|
.. | ||
combined-sampler-reuse.asm.frag | ||
default-member-names.asm.frag | ||
empty-struct.asm.frag | ||
frem.asm.frag | ||
function-overload-alias.asm.frag | ||
image-extract-reuse.asm.frag | ||
implicit-read-dep-phi.asm.frag | ||
interpolation-qualifiers-struct.asm.frag | ||
locations-components.asm.frag | ||
lut-promotion-initializer.asm.frag | ||
min-max-clamp.asm.frag | ||
op-constant-null.asm.frag | ||
pass-by-value.asm.frag | ||
phi-loop-variable.asm.frag | ||
srem.asm.frag | ||
texel-fetch-no-lod.asm.frag | ||
undef-variable-store.asm.frag | ||
unknown-depth-state.asm.frag | ||
unord-relational-op.asm.frag | ||
unreachable.asm.frag | ||
vector-shuffle-oom.asm.frag |