[vulkan] Fix loader bug in vkGetInstanceProcAddr

bug: 143609297

In vkGetInstanceProcAddr, if it's a device dispatch, and it's not Vulkan
1.0 core, ask the ResourceTracker dynamically for feature support, or
abort. This is because the spec is lenient enough to allow all functions
to be obtained from vkGetInstanceProcAddr.

This means generating new, slower versions of each entry point. Yay for
the loader spec!

Note that we should do the same thing for the global get proc address,
but a similar problem has not happened yet.

Change-Id: I58551efb11eb43254fa6fbb6a88caa56ac34ac8d
2 files changed
tree: 5f3ae1204cf5d01d65b7018d07246d3f29c68412
  1. registry/