3 ms·
The 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 cann
by legulere 10y ago
The 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.