Skip to content

[2.0] Vulkan function tables #180

Description

@Perksey

In Vulkan, function loading is both instance and device dependent. In 2.0, we want to remove the dependency on the CurrentInstance and CurrentDevice properties. This means we have a lot of work to do as currently 1.0 can be used with multiple instances and multiple devices (albeit in a bit of a hacky way) using the PurgeEntryPoints method, causing Vulkan entry points to be reloaded using the new instance and device. In 2.0, we should:

  • Remove the extension loader's dependency on the CurrentInstance and CurrentDevice properties by making the user pass in an instance and/or device when loading extensions
  • Add custom function table capabilities to SilkTouch
  • Add a device function table
  • Add an instance device function table table
  • Auto-detect usage of new instances and devices by using SilkTouch prologues with Vulkan, ensuring the function table currently in use is the right one

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions