Skip to content

Conversation

@spencer-lunarg
Copy link
Contributor

@spencer-lunarg spencer-lunarg commented Dec 25, 2023

the goal is not to dismiss #197 or #154 but instead create a more gradual first step to at least get "something" as a baseline for support

With this there is a spvReflectEnumerateSpecializationConstants which can be queried and returned a SpvReflectSpecializationConstant object.

For now SpvReflectSpecializationConstant is the bare minimum until it is better examined (and tested) what should be added, but then it will be a more simple additive process to what is already exposed

(cc @muraj @zbendefy it would be awesome to get feedback if this helps solve your problems or not)

@spencer-lunarg spencer-lunarg merged commit be73aee into KhronosGroup:main Jan 11, 2024
@spencer-lunarg spencer-lunarg deleted the spencer-spec-constant2 branch January 11, 2024 01:28
@zbendefy
Copy link
Contributor

zbendefy commented Jan 15, 2024

Hi @spencer-lunarg !
Thanks this is definitely useful, however I'm currently missing the name of the constant in SpvReflectSpecializationConstant.

The way I set things up is that I use variable names in the frontend code, that later get resolved to specialization constant ids in the backend code. So it would help me a lot if I could also access the name of the constant in 'SpvReflectSpecializationConstant'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants