Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specialization constants need to be supported on all backends, including non-Vulkan GLSL, HLSL and C++ #5794

Open
smarton-sc opened this issue Dec 7, 2024 · 4 comments
Labels

Comments

@smarton-sc
Copy link

As a follow-on to #5725, we need specialization constant support via #if expressions for backends that don't have native specialization constant constructs.

@smarton-sc smarton-sc changed the title Specialization constants need to be supported on all backends, including non-Vulkan GL, HLSL and C++ Specialization constants need to be supported on all backends, including non-Vulkan GLSL, HLSL and C++ Dec 7, 2024
@csyonghe
Copy link
Collaborator

csyonghe commented Dec 7, 2024

Please note that non-vulkan GLSL is not an officially supported backend, so it would not be possible to add without the fundamentals to add traditional GLSL as a dedicated backend first.

@smarton-sc
Copy link
Author

Oof. I was not aware. That's another hard blocker for us. We use desktop 120 (hopefully not for long) and 430, as well as ES 300 and 310.
We actually wouldn't use the HLSL and C++ backends, so spec consts in those languages are not useful for us, I just added them for completeness, ie: that slang should support specialization universally in principle.
I don't want to sound demanding, just offering context. I understand you probably have bigger fish to fry.

@bmillsNV
Copy link
Collaborator

Thank you for filing this issue. This is worth resolving, but we don’t have current available bandwidth – moving to the backlog for now. Please do feel welcome to propose a solution if you’re able to before it makes it out of the backlog!

@steel3d
Copy link

steel3d commented Jan 21, 2025

Thanks! Will do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants