Private
Public Access
1.3 KiB
1.3 KiB
← Back to Twitter thread index
title: "Vulkan starts with the ping pong between getting an instance proc addr so one ca" author: "NOTimothyLottes" handle: "@NOTimothyLottes" post_url: "https://x.com/NOTimothyLottes/status/2074108624553554387" post_id: "2074108624553554387" timestamp: "2026-07-06 12:30:05" post_count: 3 reply_count: 1 repost_count: 0 like_count: 20 view_count: 2054
@NOTimothyLottes — Vulkan starts with the ping pong between getting an instance proc addr so one ca
Post 1 (2026-07-06 12:30:05)
Vulkan starts with the ping pong between getting an instance proc addr so one can get vkCreateInstance, then using that to create an instance so one can get the remaining functions. I reuse my Lib() code modified for VK, that keeps a 64-bit base and 32-bit offsets for symbols.
Post 2 (2026-07-08 16:09:55) — reply to Post 1
@NOTimothyLottes That's very neat, but is it really true in practice that the max distance between symbols can't exceed 4GB? I think it would be a sane guarantee that it can't, but I assumed the worst and got scared off from the idea...
Post 3 (2026-07-08 16:24:40) — reply to Post 2
@nullspector It’s working thus far, if I find a case it doesn’t work I’ll change it. I keep a different base per library, so likely safe enough.