LLVM ist a mess

Posted Mar 25, 2024 7:34 UTC (Mon) by Curan (subscriber, #66186)
In reply to: LLVM ist a mess by donio
Parent article: Cranelift code generation comes to Rust

Yeah, it certainly looks that way. Though ACO was, AFAIR a decision driven purely by performance. ACO is just faster than the LLVM path.

to post comments

LLVM ist a mess

Posted Apr 11, 2024 7:24 UTC (Thu) by daenzer (subscriber, #7050) [Link] (1 responses)

Also, radeonsi hasn't switched the default from LLVM to ACO yet, and it'll probably keep the LLVM backend for some time after that. E.g. AFAIK the radeonsi ACO backend doesn't work with the rusticl frontend yet.

And that's just one driver, Mesa uses LLVM in many other places, the elephant in the room being llvmpipe.

LLVM ist a mess

Posted Apr 11, 2024 7:39 UTC (Thu) by Curan (subscriber, #66186) [Link]

Yeah, the full switch to ACO is not yet there for radeonsi. And, given corporate constraints, might never really happen.

llvmpipe I do not mind. That is a very distinct driver and allows testing for extensions. That would be easy not to build in a production environment with hardware acceleration around. llvmpipe was also very important for virtual machines (these days less). But the core Khronos and/or hardware driver stuff with LLVM dependencies I really wish I could avoid.