unified syscalls

Mike Frysinger <[email protected]>
Newsgroups gmane.comp.lib.newlib
Message-ID <YHcDL7qXQH0lFEry@vapier>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.