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.

Sign up for GitHub

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

Jump to bottom

Consider splitting up SHADER_INT64_ATOMIC_MIN_MAX further #5880

Open
JMS55 opened this issue Jun 26, 2024 · 0 comments
Open

Consider splitting up SHADER_INT64_ATOMIC_MIN_MAX further #5880

JMS55 opened this issue Jun 26, 2024 · 0 comments
Labels
type: enhancement New feature or request

Comments

@JMS55
Copy link
Contributor

JMS55 commented Jun 26, 2024

Is your feature request related to a problem? Please describe.
SHADER_INT64_ATOMIC_MIN_MAX on vulkan requires both shaderBufferInt64Atomics and shaderSharedInt64Atomics

Describe the solution you'd like
Possibly split the feature into two, or move the shared memory capability to SHADER_INT64_ATOMIC_ALL_OPS

Describe alternatives you've considered
Better document the requirements

Additional context
Intel Arc GPUs (at least on Windows + Vulkan) support only shaderBufferInt64Atomics and not shaderSharedInt64Atomics.
@teoxoy teoxoy added the type: enhancement New feature or request label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@teoxoy @JMS55