Brendan Duncan

Just tested your version and it's not quite right. I'll poke at it to see what needs to be fixed. I wasn't a fan of all the memory moves and...

Yours was close, just had a left over `program.get()`, which should have been `&program`. ``` #if SHADERC_ENABLE_WGSL_OUTPUT == 1 auto program = tint::reader::spirv::Parse(std::vector(result.begin(), result.end())); if (!program.IsValid()) { std::cout

Thanks. Yes, I'm in the process of putting together a catalog of all the types of errors we're getting. I'll share that here soon.

I'm still looking through the 1,865 shader variants being flagged with errors from a single project I've been testing, to identify the root causes of the analysis errors. So far,...

Another example of a shader that falls in the "yes, this is non-uniform, but we know what we're doing" category is from one of our UI blit shaders (example in...

What information are you looking for? I have literally thousands of shader variants with errors that could be provided to help catalog some of the analyses issues. Most of the...

For developers like us who don't write WGSL directly, marking WGSL blocks as "unsafe" or "uniform" isn't really an option. Unsafe versions of the offending functions, might work in that...

@jimblandy We use Tint to generate the WGSL from SPIR-V, so perhaps it could be extended to tag generated functions for us if such a tag existed. Otherwise the other...

It's been a while since I've been able to work on this, so I don't remember much of anything at the moment. A quick look at the code, in tar_encoder.dart...

That's certainly a possibility, but I doubt I'll have time to do it any time soon.