* unified syscalls
@ 2021-04-14 14:58 Mike Frysinger
0 siblings, 0 replies; only message in thread
From: Mike Frysinger @ 2021-04-14 14:58 UTC (permalink / raw)
To: newlib
the linux kernel has migrated to a unified syscall table so tha when a new
syscall is added, every arch doesn't have to explicitly wire it up. there
are also common C entry points that arches largely get for free.
i grok that newlib provides the common C library and libgloss is the glue
between the <whatever runtime> and the common C library. but it still has
a ton of duplication that is largely unnecessary. i wonder if we can't do
better here.
the reason this comes up is that monitors that need to implement the syscalls
have to eat this duplicated pain too. if libgloss had a unified layer here,
it'd make my life easier.
thoughts ?
-mike
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-04-14 14:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-14 14:58 unified syscalls Mike Frysinger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).