How to build includes without enabling "GL_GOOGLE_include_directive" extension?

[ghost]

Hello. I have problems with Nvidia. How to disable output of "GL_GOOGLE_include_directive" codes in productive shaders?

[antiagainst]

Hi @acterhd,

Do you mean removing the OpSourceExtension GL_GOOGLE_include_directive line in the generated SPIR-V binary module? That actually can be done via the -Os option on glslc (or SetOptimizationLevel for the library API). Yeah, that also runs some other optimization stuff, but I think it's beneficial for productive code. More fine-grained controlling is something not supported yet and should be a TODO.

Hope this solves your problem. Let me know if I am not answering your question. Thanks!

[ghost]

In glslc none this flag... Even if I built from source. Used old version...

Also, issues with

./shaders/voxelizer/voxelizer.vert.spv


./shaders/voxelizer/voxelizer.geom.spv


./shaders/voxelizer/voxelizer.frag.spv

Geometry info
-------------
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)
error: binding mismatch between shaders for SSBO (named __defaultname)

Fragment info
-------------
(0) : fatal error C9999: *** exception during compilation ***

Link info
---------
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders
error: different buffer variables (named  and ) sharing the same offset within a storage block (named ) between shaders

[antiagainst]

Hmm, now I'm suspecting that the driver compiler is using debug instruction for some meaningful stuff (use OpName for interface matching, etc. which is why the above errors since -Os removes all debug instructions), which is not supposed to be the case: https://www.khronos.org/registry/spir-v/specs/1.0/SPIRV.html#OpSourceExtension. (Notice the "no semantic impact and can safely be removed from a module" part, which means, with or without OpSourceExtension/OpName, the module should just work fine.)

Could you provide the original error from the driver compiler before applying -Os? Thanks!

[ghost]

Okay.... I can't load any compute shader from SPIR-V in OpenGL...
I tried all variants.

[antiagainst]

Oh, glad to see you've figured out this by yourself. Sorry didn't provide much help. I'll close this for now.

[ghost]

I anyway can't load SPIR-V modules...

[dneto0]

Loading SPIR-V into OpenGL is a recently-ratified extension.
https://www.opengl.org/registry/specs/ARB/gl_spirv.txt
I'd first check to make sure that your driver supports that extension.