| 17 Jul 2025 |
 olivia | probably use_llvm is about using the llvm shader compiler middle/backend instead of the nir one | 02:57:20 |
| olivia | I suspect nobody has implemented fp8 or cmats in the llvm backend yet | 02:57:51 |
 woobilicious | Yeah I'd just think it would have feature parity, but I guess not. | 02:57:58 |
| olivia | I wouldn't expect it to, nobody likes it lol | 02:58:25 |
| olivia | I believe the intention is to remove it eventually, but I'm not very aware of what's going on with amd stuff so take that with a grain of salt | 02:58:51 |
| olivia | https://docs.mesa3d.org/drivers/radv.html#shader-compilation yeah
We still maintain an LLVM based compiler backend too, which is these days solely used for testing and hardware bringup. Users are recommended NOT to use the LLVM backend.
| 02:59:54 |
| woobilicious | Oh really? how is that related to the ACO compiler? doesn't that use llvm? | 03:00:08 |
| olivia | no ACO is NIR only | 03:00:44 |
| woobilicious | ahh my memory is wrong then. | 03:01:31 |
| olivia | (I believe the llvm backend in radeonsi predates NIR) | 03:01:33 |
| woobilicious | olivia: I think the FSR4 code just converts to fp16 manually instead of them extending the compiler to do the conversion. I guess the code is writting to use cooperative_matrix, so yeah only RDNA3...too bad I wanted slow as dogshit FSR4 haha. | 03:33:25 |
| olivia | yeah, that seems plausible (I don't know anything about the specifics of FSR4, but almost certainly it will not work without cmats) | 04:10:31 |
