KhronosGroup / KhronosGroup/Vulkan-Loader
Is it legal to get "vkGetDeviceProcAddr" from "vkGetDeviceProcAddr"?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 696
- Forks
- 343
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 17
Description
In common cases, we get function entry point vkGetDeviceProcAddr by calling myLayer.vkGetInstanceProcAddr( "vkGetDeviceProcAddr").
However, I met some cases that user calls myLayer.vkGetDeviceProcAddr("vkGetDeviceProcAddr") . Regardless of whether it makes sense to do so, I am more concerned about whether this behavior is defined in the spec of Vulkan loader. I have seen layers that returns vkGetDeviceProcAddr of itself, and I have also seen layers returns nothing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Vulkan loader specification and the reported calls to vkGetInstanceProcAddr and vkGetDeviceProcAddr. Compare the behavior where a layer returns its own vkGetDeviceProcAddr with behavior where it returns nothing, then document the defined expectation and any required consistency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100