From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: "caiyinyu@loongson.cn" <caiyinyu@loongson.cn>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>
Subject: [PATCH v2 0/5] linux: Avoid va_list for generic syscall wrappers if possible
Date: Tue, 4 Apr 2023 10:12:27 +0000 [thread overview]
Message-ID: <PAWPR08MB8982FAD88EF6C897AEE3A85083939@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
Hi,
> So I believe that the assembly implementation of syscalls is still
> necessary, especially for users who are using GCC<=13.
As far as I can tell, all internal syscalls are inlined so they never use
syscall() and thus don't have this issue. Does that not happen on
LoongArch? If not, you might need something to enable the inlining.
It's not clear to me how often syscall() is used by user code instead of
direct calls to read() etc. So is it really necessary to consider optimizing
syscall()? Are there microbenchmarks that use it?
Also does sysdeps/unix/sysv/linux/riscv/syscall.c work for you?
So I think we can avoid unnecessary assembly code.
Cheers,
Wilco
next reply other threads:[~2023-04-04 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 10:12 Wilco Dijkstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-05 13:19 Wilco Dijkstra
2023-04-05 14:04 ` Adhemerval Zanella Netto
2023-04-07 7:31 ` caiyinyu
2023-03-25 14:08 Xi Ruoyao
2023-03-27 14:04 ` Carlos O'Donell
2023-03-27 14:44 ` Xi Ruoyao
2023-03-27 14:45 ` Xi Ruoyao
2023-03-27 14:51 ` Xi Ruoyao
2023-04-04 1:25 ` caiyinyu
2023-04-04 12:12 ` Xi Ruoyao
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=PAWPR08MB8982FAD88EF6C897AEE3A85083939@PAWPR08MB8982.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=caiyinyu@loongson.cn \
--cc=libc-alpha@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).