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

Clarify how VK_WHOLE_SIZE works with dynamic offset #1546

Closed
sfricke-samsung opened this issue Jun 1, 2021 · 2 comments
Closed

Clarify how VK_WHOLE_SIZE works with dynamic offset #1546

sfricke-samsung opened this issue Jun 1, 2021 · 2 comments
Assignees
@sfricke-samsung
Labels
Resolving Inside Khronos

Comments

@sfricke-samsung
Copy link

From KhronosGroup/Vulkan-ValidationLayers#2846

The phrase effective range in the spec in currently not clear and ambiguous

Need to make more clear that how the end point of a buffer's range is baked into the descriptor on some GPUs
@sfricke-samsung sfricke-samsung self-assigned this Jun 1, 2021
@sfricke-samsung sfricke-samsung mentioned this issue Jun 1, 2021
Closed
@sfricke-samsung sfricke-samsung mentioned this issue Sep 16, 2021
Closed
@oddhack
Copy link
Contributor

oddhack commented Nov 23, 2021

@sfricke-samsung did this get an internal tracker? I can't find one.

@sfricke-samsung sfricke-samsung mentioned this issue Jan 21, 2022
Merged
@oddhack
Copy link
Contributor

oddhack commented Apr 5, 2022

This should be fixed in the 1.3.211 spec update.

@oddhack oddhack closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sfricke-samsung sfricke-samsung

Labels
Resolving Inside Khronos
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oddhack @sfricke-samsung