Linux 6.9 To Allow RISC-V Kernel Builds With Clang Link-Time Optimizations

[phoronix]

Phoronix: Linux 6.9 To Allow RISC-V Kernel Builds With Clang Link-Time Optimizations

Adding to the list of features slated for the upcoming Linux 6.9 cycle is allowing RISC-V kernel builds to be compiled with Clang Link-Time Optimizations (LTO) enabled...

https://www.phoronix.com/news/RISC-V-With-Clang-LTO-Linux-6.9

[JEBjames]

Michael

typo

"as well as Clang;s" should be "Clang's" (apostrophy)

[Volta]

It seems Clang isn't so good atm:

https://lkml.org/lkml/2024/1/6/180

Can you please push the clang people to not do the stupid thing they
do now, which is to say "oh, I can use registers _or_ memory, so I'll
always use memory".

Btw, it's actually much worse than that, and clang is just doing
incredibly broken things. Switching to "r" just hides the garbage.

Anyway, this is *literally* a clang bug. Complain to clang people for
being *extra* stupid - we told the compiler that it can use a register
or memory, and clang decided "I'll use memory", so then when we gave
it a memory location, it said "no, not *that* memory - I'll just
reload it on stack".

In contrast, gcc gets this right