Cleanup VK_EXT_debug_utils section - #392
Merged
spencer-lunarg merged 1 commit intoJul 27, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Inspired by my talk with @iradicatoratfb about using
vkCmdInsertDebugUtilsLabelEXTWhile here, I removed some extra stuff I felt was not useful trying to read this chapter myself
vkGetInstanceProcAddris just noise, this section should assume that is knownVK_EXT_debug_utilsburied in the "migrate fromVK_EXT_debug_markersection... moved it up as hopefully after YEARS now one is still onVK_EXT_debug_marker