<anholt>
hoping you've got something laying around for samplemask. I tried hacking various things in to make samplemask make more sense to me, with no luck.
<zmike>
uhh
<zmike>
I can take a look, not entirely sure what the issue is
<anholt>
messing around with fixing this cs is not really where I should be focusing. it's just that when I dumped shaders it made it hard to find any other shader's content :)
<zmike>
yeah I always groan when I see the results of this in something I need to debug
<anholt>
oh, and this MR had some store type mismatches once !18259 lands
<anholt>
(16 vs 32)
<zmike>
grimace
<anholt>
possibly store_shared and friends need uint_type to use the instr's bit_size?
<zmike>
uhhh
<zmike>
hm
<anholt>
oh, but in that theory this MR shouldn't be implicated, then.
<zmike>
tentative yes in that I think I might have handled the zink_compiler part for that correctly?
<anholt>
and, yeah. looks like that MR does break zink+turnip. will sort that out.
<zmike>
almost figured out the samplemask thing...
<zmike>
what the
<zmike>
ohhhhhh
<zmike>
hahaha
<zmike>
this is from before erik saved us all with type caching
<kusma>
??? :)
<kusma>
some manual caching left over somewhere? :)
<zmike>
ugh this is really stupid...
<zmike>
anholt: how do builtin function temps work with variable locations?
<anholt>
not sure what you mean?
<zmike>
like in this test there's a function temp samplemask variable
<zmike>
it has location=FRAG_RESULT_SAMPLE_MASK
<zmike>
is that reliable for temp vars in fragment stage?
<zmike>
or coincidence
<anholt>
coincidence, you shouldn't be looking at the location for a function temp
<zmike>
didn't think so
<zmike>
hmmmm
<zmike>
ah
<zmike>
I was looking too deep
<anholt>
"Type mismatch for SPIR-V SSA value 369636 bytes into the SPIR-V binary" what if I don't want to look 370kb into a spirv binary, huh? have you considered that?