3 ms·
Amazing how much credit AMD gets for “open sourcing” things when so much of the functionality is in binary blobs. Like this entire directory: https://github.co
by throwaway62831 4y ago
Amazing how much credit AMD gets for “open sourcing” things when so much of the functionality is in binary blobs.
Like this entire directory:
https://github.com/GPUOpen-Tools/radeon_raytracing_analyzer/tree/main/shaders https://github.com/GPUOpen-Tools/radeon_raytracing_analyzer/...
- PedroBatista 4y agoWhen NVIDIA is the benchmark, everybody is a saint on Earth.
- kllrnohj 4y agoVulkan requires you to ship shaders in spir-v format, it doesn't have a source-level shader language. The generous interpretation is AMD just forgot to ship the source for those spir-v blobs since it would be a different toolchain. Looking at the size of the blobs, though, I'm not entirely sure why you're claiming "so much" of the functionality is in those blobs. Most of them you could probably pretty trivially disassmeble & understand, especially given all the inputs & outputs are not obfuscated. And the actual function code of many of them look to be relatively small.
- JBits 4y agoEven if the functionality is in binary blobs, can open source drivers still take advantage of this?
- q-big 4y agokllrnohj already wrote that Vulkan has no predefined source code language for shaders. I can imagine that the SPIR-V code of these shaders could have been hand-optimized by some team at AMD, so a textual reprsentation of this binary code is the version that the engineers at AMD work on. Also: the license of the repository is MIT license, so you are free to reverse-engineer these shaders and port them to a high-level language of your choice.