Initial support for NonSemantic.Shader.DebugInfo 101

[dnovillo]

This implements NSDI.101 (KhronosGroup/SPIRV-Registry#390) in glslang. It updates SPIRV-Tools and SPIRV-Headers dependencies to bring in the new headers for NSDI.101.

Version promotion

To minimize disruption with existing tools, glslang will always generate an import of NonSemantic.Shader.DebugInfo.100. If the module uses an opcode that requires NSDI.101 (cooperative types and new floating point types), it then changes the import string to .101. The promotion is done by patching the OpExtInstImport instruction's string operand.

The entry point is Builder::requireNonSemanticShaderDebugInfoVersion. Each of the three new emitter functions
calls it unconditionally before emitting the instruction.

New emitters

• Builder::makeVectorIdDebugType: emits DebugTypeVectorIdEXT. Called from makeCooperativeVectorTypeNV when emitNonSemanticShaderDebugInfo is set.
• Builder::makeCooperativeMatrixDebugTypeKHR: emits DebugTypeCooperativeMatrixKHR. Replaces the former opaque-composite workaround in makeCooperativeMatrixTypeKHR.
• Builder::makeFloatDebugType: extended with an optional fpEncoding operand. The three float-8 and bfloat16 type builders (makeBFloat16Type, makeFloatE5M2Type, makeFloatE4M3Type) now handle the new floating point types.

Header rename

This needed to import the new NonSemanticShaderDebugInfo.h from SPIRV-Headers. This means that all the previous C identifiers that had 100 embedded in them needed to change. Those changes are mechanical, there is no functional change there.

I also added a section in README.md to document how to update this headers in future revisions of NSDI.

Tests

I replaced the previous golden output tests spv.debuginfo.coopmatKHR.comp with a new unit test file gtests/SpvDebugInfoTest.cpp. All the NSDI.101 opcodes are tested there.

[dnovillo]

For reference, these are the PRs adding NSDI.101 support:

• SPIRV-Headers: Add NSDI 101 instructions SPIRV-Headers#579
• SPIRV-Tools: Add validation for NSDI 101 SPIRV-Tools#6635

[jeremy-lunarg]

Can this test be removed?

[arcady-lunarg]

LGTM aside from Jeremy's comment. Before I merge, could you squash this into just two or three commits? One for the rename of the header file and associated enumeration values and the other one for the "initial implementation"? And the tests can go in their own commit or together with the implementation.