On Mai 11 2020, Linus Torvalds wrote: > Why is glibc doing it in the first place? Is it some historical thing > that is simply irrelevant on RISC-V simply because RISC-V doesn't have > that kind of history, perhaps?
It is completely generic. Even new architectures become old over time and accumulate cruft. The idea is that if you configure glibc with --enable-kernel=VERSION, it assumes that all syscalls from kernel VERSION are guaranteed to exist, and drops the fallbacks for those syscalls, or uses them in the first place (if no useful fallback existed). From time to time the absolute minimum supported kernel version is increased (this happend the last time in 2017, when x86 and x86_64 moved the mininum from 2.6.32 to 3.2, after all other architectures did that step in 2016), which allows removing the fallback code that becomes obsolete. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."