Missing content in spec.json

[GeForceLegend]

Maybe there is some more. Below is just what I found:

All keywords (well, just terminateInvocation from GL_EXT_terminate_invocation afaik) and types from extensions

constants:

• from GL_KHR_memory_scope_semantics

const int gl_ScopeDevice      = 1;
const int gl_ScopeWorkgroup   = 2;
const int gl_ScopeSubgroup    = 3;
const int gl_ScopeInvocation  = 4;
const int gl_ScopeQueueFamily = 5;
const int gl_SemanticsRelaxed         = 0x0;
const int gl_SemanticsAcquire         = 0x2;
const int gl_SemanticsRelease         = 0x4;
const int gl_SemanticsAcquireRelease  = 0x8;
const int gl_SemanticsMakeAvailable   = 0x2000;
const int gl_SemanticsMakeVisible     = 0x4000;
const int gl_SemanticsVolatile        = 0x8000;
const int gl_StorageSemanticsNone     = 0x0;
const int gl_StorageSemanticsBuffer   = 0x40;
const int gl_StorageSemanticsShared   = 0x100;
const int gl_StorageSemanticsImage    = 0x800;
const int gl_StorageSemanticsOutput   = 0x1000;

• from GL_KHR_cooperative_matrix

const int gl_MatrixUseA             = 0;
const int gl_MatrixUseB             = 1;
const int gl_MatrixUseAccumulator   = 2;
const int gl_CooperativeMatrixLayoutRowMajor        = 0;
const int gl_CooperativeMatrixLayoutColumnMajor     = 1;
const int gl_MatrixOperandsSaturatingAccumulation   = 0x10;

functions: (looks like missing functions are always the first function in an extension description file?)

• traceRayEXT() from GL_EXT_ray_tracing
• traceRayMotionNV() from GL_NV_ray_tracing_motion_blur
• hitObjectTraceRayNV() from GL_NV_shader_invocation_reorder

[nolanderc]

Yeah, gen_spec.py is a messy bunch of regexes to try and make sense of the plain-text specs, so it’s expected that things are missing. It’s great that you report these things, as it’s hard to know if there’s anything that was missed when there are so many extensions… I will have a look when I find the time!