4 ms·
At the very least AMD made an extension pretty much immediately[1,2]. NVidia... well I don’t really expect graphics-programming-friendly initiatives from NVidia
by mananaysiempre 2y ago
At the very least AMD made an extension pretty much immediately[1,2]. NVidia... well I don’t really expect graphics-programming-friendly initiatives from NVidia at this point.
[1] https://gpuopen.com/gpu-work-graphs-in-vulkan/ https://gpuopen.com/gpu-work-graphs-in-vulkan/
[2] https://github.com/KhronosGroup/Vulkan-Docs/blob/main/proposals/VK_AMDX_shader_enqueue.adoc https://github.com/KhronosGroup/Vulkan-Docs/blob/main/propos...
- deleted 2y ago[deleted]
- pjmlp 2y agoWrong there, as Slang is the only sane alternative to a stagnant GLSL, unless you favour using DirectX HLSL.
- creata 2y agoAs far as I can tell, AMD's extension is supported by exactly one version of AMD's driver, and it's outdated and only on Windows. https://vulkan.gpuinfo.org/listdevicescoverage.php?extension=VK_AMDX_shader_enqueue&platform=all https://vulkan.gpuinfo.org/listdevicescoverage.php?extension... https://github.com/KhronosGroup/Vulkan-Docs/issues/2336 https://github.com/KhronosGroup/Vulkan-Docs/issues/2336 https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-VLK-23-10-01-43.html https://www.amd.com/en/resources/support-articles/release-no...
- my123 2y agoVK_NV_device_generated_commands(_compute), which is already implemented by RADV in Mesa, and is much older than VK_AMDX_shader_enqueue. The X suffix means that it's not a stable API and should not be used by shipped code.
- creata 2y agoSo are the concerns regarding VK_NV_generated_commmands (mainly, unnecessary latency) in the VK_AMDX_shader_enqueue proposal overstated?
- my123 2y agoIt comes with a lot of flexibility that the equivalent AMDX extension doesn't have, including being able to queue graphics shaders, not compute ones only. As far as I can see, unnecessary latency isn't actually a problem.