From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Nicholas Piggin <npiggin@gmail.com>,
"Dmitry V. Levin" <ldv@altlinux.org>
Cc: libc-alpha@sourceware.org, musl@lists.openwall.com,
linux-api@vger.kernel.org, libc-dev@lists.llvm.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Linux powerpc new system call instruction and ABI
Date: Wed, 19 May 2021 09:39:33 -0300 [thread overview]
Message-ID: <87r1i2kid6.fsf@linux.ibm.com> (raw)
In-Reply-To: <1621421721.r9fefebis8.astroid@bobo.none>
Nicholas Piggin via Libc-alpha <libc-alpha@sourceware.org> writes:
> As a more hacky thing you could make a syscall with -1 and see how
> the error looks, and then assume all syscalls will be the same.
I'm not sure this would work.
Even in glibc, it's expected that early syscalls will use sc while scv is used
later in the execution.
--
Tulio Magno
next prev parent reply other threads:[~2021-05-19 12:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200611081203.995112-1-npiggin@gmail.com>
[not found] ` <20210518231331.GA8464@altlinux.org>
2021-05-19 2:50 ` Nicholas Piggin
2021-05-19 5:01 ` Nicholas Piggin
2021-05-21 19:40 ` Matheus Castanho
2021-05-21 19:52 ` Florian Weimer
2021-05-21 20:00 ` Matheus Castanho
2021-05-21 20:52 ` Dmitry V. Levin
2021-05-24 12:11 ` Matheus Castanho
2021-05-24 20:33 ` Matheus Castanho
2021-05-19 10:24 ` Dmitry V. Levin
2021-05-19 10:59 ` Nicholas Piggin
2021-05-19 12:39 ` Tulio Magno Quites Machado Filho [this message]
2021-05-19 13:26 ` Dmitry V. Levin
2021-05-19 22:51 ` Nicholas Piggin
2021-05-19 23:27 ` Dmitry V. Levin
2021-05-20 2:40 ` Nicholas Piggin
2021-05-20 3:06 ` Dmitry V. Levin
2021-05-20 5:12 ` Nicholas Piggin
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=87r1i2kid6.fsf@linux.ibm.com \
--to=tuliom@ascii.art.br \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-dev@lists.llvm.org \
--cc=linux-api@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=musl@lists.openwall.com \
--cc=npiggin@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).