6 ms·
Spir-v is already happening: https://rocm.blogs.amd.com/software-tools-optimization/spir-v-rocm/README.html https://rocm.blogs.amd.com/software-tools-optimizati
by nolist_policy 2mo ago
Spir-v is already happening: https://rocm.blogs.amd.com/software-tools-optimization/spir-v-rocm/README.html https://rocm.blogs.amd.com/software-tools-optimization/spir-...
- stevefan1999 2mo ago> PYTORCH_ROCM_ARCH="gfx900;gfx906;gfx908;gfx90a;gfx942;gfx950;\ gfx1030;gfx1100;gfx1101;gfx1102;gfx1103;\ gfx1150;gfx1151;gfx1200;gfx1201" That kicked off my PTSD to setup ROCm on my 6600XT and 9070XT, not even with different containers. I have to build an image for EACH architecture. That's duping 15GB for each arch on my already terribly small SSD.
- ktm5j 2mo agoWell, that appears to be the exact problem that they're trying to solve with spir-v. > The shift SPIR-V enables is from ahead-of-time compilation per target to compile once, just-in-time specialize on device.