Re:The perils of transition to 64-bit time_t
by mort96 on Saturday September 28, 2024 @07:43PM
(#41683693)
Splitting libc into one "stable kernel API" part and one "library with things which are useful to C programmers" part would honestly make a ton of sense. OSes which declare their syscall interface to be unstable would be more convincing if they actually provided a stable API that's intended for other consumers than C.
[ Parent
| on HN ]
Re:The perils of transition to 64-bit time_t
by AshamedCaptain on Saturday September 28, 2024 @08:16PM
(#41683820)
Frankly I don't see the point of complaining that libc is not useful for non-C consumers. Sure, there are some ancillary functions in libc you'll likely never call. But what's the issue with making syscalls through libc? Again, the only difference is what the very last call instruction is. If your runtime can marshal arguments for the kernel, then it surely can marshal arguments for libc. They are almost always practically the same ABI.
And you can avoid the need for VDSO-like hacks which is basically the kernel exposing a mini-libc to userspace.
Re:The perils of transition to 64-bit time_t
by db48x on Sunday September 29, 2024 @11:45AM
(#41688133)
This is the reason why Rust compiles every program statically, except that the resulting “static” binary still has to link against libc.