From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: unified syscalls
Date: Wed, 14 Apr 2021 10:58:55 -0400 [thread overview]
Message-ID: <YHcDL7qXQH0lFEry@vapier> (raw)
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
reply other threads:[~2021-04-14 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YHcDL7qXQH0lFEry@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).