Update to upstream SPIR-V 1.5.2

[Jasper-Bekkers]

This removes the internal version of spirv.core.grammar.json and switches to use only the upstream one spirv.core.grammar.json file as discussed in #116 as a potential better way forward.

This also updates all the bindings to SPIR-V 1.5.2

[Jasper-Bekkers]

Looks like I can't add reviews but @antiagainst and @kvark should look at this.

[kvark]

Thank you, that looks like an outstanding piece of work!

[Jasper-Bekkers]

Looks like rspirv/dr/build/autogen_norm_insts.rs isn't generated properly.

[Jasper-Bekkers]

I think there may be a bit more work to do - it's a pretty big change in a mostly unfamiliar codebase so an extra pair of eyes would definitely help, but I think I have a significant part of it covered.

Do we have some kind of automated test suite to test against?

[kvark]

@Jasper-Bekkers do you exist on the Matrix for a short chat, e.g. on #gfx:matrix.org?
The situation is a bit troublesome:

1. the project has 3 levels of complexity on top of each other: bindings, data representation (DR), structured representation (SR)
2. @antiagainst - the creator of the project - has little time to develop this, but they can look at changes sometimes
3. we (gfx-rs org) wanted to took over the project and use it for our shader translation needs, contributing to the SR heavily. However, we gave up and are no longer interested in either DR or SR in rspirv. We only use spirv-headers from rspirv. We are building the swizz army knife of shader translation in https://github.com/gfx-rs/naga now.

Therefore, there is hardly anyone to help you land these changes and review them (with respect to DR/SR parts), unfortunately (sorry!).
There is a solution, however. If @antiagainst doesn't mind, I can add you as a maintainer, and you'll be able to shape the DR/SR more towards your needs. Perhaps, it would make sense to move the whole project under Embark, even?
Let me know what you think.

[kvark]

@antiagainst how do you feel about spirv-headers being moved out to the Khronos github organization?
It looks like DR/SR will be left unmaintained after that, but it's better than trying to drag them along at this point.

[Jasper-Bekkers]

Thanks @kvark for making me a maintainer of this project. I too mostly use it for spirv-headers and have done the last two updates now to new versions of SPIR-V so I think it makes a lot of sense.

I've been developing a bit against this version of the library and I haven't run into any oddities at least. Would be good to get some eyes on this and #133 and then merge them in and publish a new version.

[Jasper-Bekkers]

Since I'm starting to get PRs to my fork of this work, I think I'll go ahead and merge this to mainline to prevent fork-of-fork situations. If anyone objects, feel free to reach out to me or revert the PR.