5 ms·
One issue with that idea is that the source code for implementing a system call is necessarily compiler-specific, it is not standard C. So, the issue would beco
by tacostakohashi 8y ago
One issue with that idea is that the source code for implementing a system call is necessarily compiler-specific, it is not standard C. So, the issue would become which compiler (version) should the source code of the include/ and src/ be for? GCC? Clang?
- olliej 8y agoA lot of the problems occur in things like struct layout of syscall arguments, which would be cross platform. But then you run into the problem of how willing to commit to ABI stability in a non-posix API. I assume there’s some commitment to such at the moment, but how much also depends on *libc abstracting them? Libcs always seem to (to me) be approximately kernel version specific
- Aic1kuir 8y agoAncient glibc versions run ok on current kernels, you're just missing out on some newer features. Otherwise statically linked binaries would cease to work.
- zaarn 8y agoThere is still a limit, very old software doesn't run anymore, largely because something in the kernel broke it. But it has been years and nobody complained so nobody will revert this or fix it. Linus has stated as such and I think a few other maintainers agree there. If you don't find the problem until years later, chances are, too few people care.