| 17 Jul 2025 |
 olivia | oh, VK_KHR_cooperative_matrix has 8-bit int/uints. !36117 is presumably about that | 01:26:22 |
|  nyanbinary 🏳️⚧️ set a profile picture. | 01:27:34 |
| olivia | and cmats are only enabled on gfx11+ | 01:27:47 |
 woobilicious | the && !pdev->use_llvm portion hints that if you can use llvm, you can get float8 support irrespective of the hardware? | 02:50:34 |
|  mall0c joined the room. | 02:52:28 |
| woobilicious | oh wait I'm getting my logic wrong...But that is more confusing, I'd think llvm wouldn't disable a feature. | 02:52:43 |
| 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 |
