From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Matheus Afonso Martins Moreira <matheus.a.m.moreira@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Re: [RFC] Linux system call builtins
Date: Mon, 8 Apr 2024 15:00:37 +0100 [thread overview]
Message-ID: <CAH6eHdTkLxc7=VGFKrSz=a8HOyHrA4YmXqomTc7=e=RBi6mYEg@mail.gmail.com> (raw)
In-Reply-To: <2852e1ff0081b5fbc3db1c3f1b627e3e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Mon, 8 Apr 2024, 13:00 Matheus Afonso Martins Moreira via Gcc, <
gcc@gcc.gnu.org> wrote:
>
> Compiler support for system calls help by eliminating the need for the
> system call stub functions traditionally provided by these C libraries.
> There's no need to link against the C libraries just for that anymore
> and there's also no need to implement it ourselves since the compiler
> provides it. The result is it makes it easier to develop freestanding
> software targeting Linux.
>
It means you don't need newlib just for the syscall function, but then you
would also need to implement memcpy, etc. for yourself. Obviously some bare
metal code needs to do that anyway, but that wouldn't be using syscalls
either.
This isn't my field so maybe I'm totally wrong, but the use case seems like
a niche within a niche, but with a non-zero maintenance burden for GCC.
next prev parent reply other threads:[~2024-04-08 14:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 9:19 Matheus Afonso Martins Moreira
2024-04-08 9:58 ` Jonathan Wakely
2024-04-08 11:59 ` Matheus Afonso Martins Moreira
2024-04-08 14:00 ` Jonathan Wakely [this message]
2024-04-08 11:24 ` Florian Weimer
2024-04-08 11:44 ` Alexander Monakov
2024-04-08 11:50 ` Florian Weimer
2024-04-08 13:01 ` Alexander Monakov
2024-04-08 13:37 ` Matheus Afonso Martins Moreira
2024-04-08 18:18 ` Paul Iannetta
2024-04-08 18:26 ` Andrew Pinski
2024-04-08 20:01 ` Paul Iannetta
2024-04-08 20:20 ` Paul Koning
2024-04-10 1:48 ` Matheus Afonso Martins Moreira
2024-04-10 13:15 ` Paul Koning
2024-04-10 14:10 ` Matheus Afonso Martins Moreira
2024-04-10 1:26 ` Matheus Afonso Martins Moreira
2024-04-08 20:24 ` Paul Floyd
2024-04-10 2:19 ` Matheus Afonso Martins Moreira
2024-04-09 11:45 ` Szabolcs Nagy
2024-04-10 2:59 ` Matheus Afonso Martins Moreira
2024-04-10 11:04 ` Szabolcs Nagy
2024-04-10 14:00 ` Matheus Afonso Martins Moreira
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='CAH6eHdTkLxc7=VGFKrSz=a8HOyHrA4YmXqomTc7=e=RBi6mYEg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=matheus.a.m.moreira@gmail.com \
/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).