3 ms·
The thing that has delayed Linux on RISC-V is simple enough: They keep changing and breaking ABIs. There was even one massive source break (changing #ifdef __r
by rwmj 10y ago
The thing that has delayed Linux on RISC-V is simple enough: They keep changing and breaking ABIs. There was even one massive source break (changing #ifdef __riscv64 to __riscv) which broke several projects that I'd contributed RISC-V support to.
The reason that the Fedora port is on hold is because I'm waiting for everything to go upstream so that this sort of thing stops happening.
IMO this was entirely avoidable, and would have meant that we could have had both Fedora and Debian full RISC-V ports one or two years ago.
- legulere 10y agoThe way I understand it, those breakages happened because problems were found during porting. So it is kind of an egg-hen problem. Without porting problems cannot get fixed and in a stable state. Without a stable state people do not want to port things.
- rwmj 10y agoThey could have maintained backwards compatibility (eg. by still defining #define __riscv64 as a deprecated definition), but chose not to. More of a problem is there was no real process for making the changes or informing anyone about the changes, they "just happened" and we only noticed later. Anyway, once glibc & kernel changes are upstream, we'll have the stable ABIs we need. I'm very much hoping that upstreaming will be completed this year.
- phkahler 10y ago>> The reason that the Fedora port is on hold is because I'm waiting for everything to go upstream so that this sort of thing stops happening. Fortunately that is happening. GCC 7 now has RISC V support and will be the compiler for Fedora 26. They really do need to get the priv spec finalized so kernel patches can go upstream as well. It's falling into place slower than people (both of us included) would like, but it is happening much more so than it did for Power, Sparc, or OpenRisc.