From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] syscall(2): fix ia64 registers
Date: Tue, 31 Dec 2013 00:26:39 +1300 [thread overview]
Message-ID: <52C1586F.7040301@gmail.com> (raw)
In-Reply-To: <1388237367-12871-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
On 12/29/13 02:29, Mike Frysinger wrote:
> The original list of registers was created by confusing strace source
> code -- this is for parsing legacy 32bit code (which is dead and no one
> cares). Update the list to reflect native ia64 syscall interface.
Thanks, Mike. Applied.
Cheers,
Michael
> Signed-off-by: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
> ---
> man2/syscall.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index de96c94..e712b41 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -159,7 +159,7 @@ arm/OABI swi NR - a1 NR is syscall #
> arm/EABI swi 0x0 r7 r0
> blackfin excpt 0x0 P0 R0
> i386 int $0x80 eax eax
> -ia64 break 0x100000 r15 r10/r8
> +ia64 break 0x100000 r15 r10/r8 bool error/errno value
> parisc ble 0x100(%sr2, %r0) r20 r28
> s390 svc 0 r1 r2 NR may be passed directly with
> s390x svc 0 r1 r2 "svc NR" if NR is less than 256
> @@ -184,7 +184,7 @@ arm/OABI a1 a2 a3 a4 v1 v2 v3
> arm/EABI r0 r1 r2 r3 r4 r5 r6
> blackfin R0 R1 R2 R3 R4 R5 -
> i386 ebx ecx edx esi edi ebp -
> -ia64 r11 r9 r10 r14 r15 r13 -
> +ia64 out0 out1 out2 out3 out4 out5 -
> parisc r26 r25 r24 r23 r22 r21 -
> s390 r2 r3 r4 r5 r6 r7 -
> s390x r2 r3 r4 r5 r6 r7 -
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-12-30 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 13:29 [PATCH] syscall(2): fix ia64 registers Mike Frysinger
[not found] ` <1388237367-12871-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2013-12-30 11:26 ` Michael Kerrisk (man-pages) [this message]
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=52C1586F.7040301@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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 NNTP newsgroup(s).