[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20261019172125.GH3542221@port70.net>
Date: Mon, 19 Oct 2026 19:21:25 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH v2] aarch64: workaround for syscalls with sve
* Rich Felker <dalias@...c.org> [2026-10-19 11:56:59 -0400]:
> On Mon, Oct 19, 2026 at 04:50:10PM +0200, Szabolcs Nagy wrote:
> > src/internal/aarch64/__syscall4.S | 12 ++++++++++++
> > src/internal/aarch64/__syscall5.S | 13 +++++++++++++
> > src/internal/aarch64/__syscall6.S | 14 ++++++++++++++
>
> I'm not sure it makes sense to separate these out into 6 files when
> they're each so small. It's a tradeoff between a few bytes in linked
> output and moving further towards command line limits running ar and
> the libc.so link. It might be okay, just something to consider.
ok moved to one file.
> I wonder if we should, instead of just using __syscallN as the
> external name, have alt inlines of __syscallN that call __syscallN_asm
> with nr moved to the end of the argument list. Then all __syscallN_asm
> look like:
>
> __syscall6:
> mov x8, x6
> svc 0
> ret
used __syscallN as the identifier in c code and
__syscallN_asm as the symbol for the extern asm code.
View attachment "v3-0001-aarch64-workaround-for-syscalls-with-sve.patch" of type "text/x-diff" (4810 bytes)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
