From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Paul Burton <paul.burton@mips.com>,
Firoz Khan <firoz.khan@linaro.org>,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
y2038 Mailman List <y2038@lists.linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v3 0/6] mips: system call table generation support
Date: Thu, 06 Dec 2018 17:43:00 -0000 [thread overview]
Message-ID: <alpine.LFD.2.21.1812061729340.4294@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1812061719180.12167@digraph.polyomino.org.uk>
On Thu, 6 Dec 2018, Joseph Myers wrote:
> > So how are `SYS_<name>' macros generated that land in <bits/syscall.h>?
>
> By gen-syscall-h.awk, which generates #ifdef conditionals for each
> possible __NR_* name (as listed in syscall-names.list in glibc).
I seem to remember having to take extra care with how the three MIPS ABIs
wire the syscalls to get it right in glibc, but I take it then this has
been now addressed reliably enough for the glibc not to care how exactly
<asm/unistd.h> has been arranged.
Given my current level of involvement with the MIPS architecture I take
your word for it and will not investigate it any further. Thanks for your
input.
Maciej
next prev parent reply other threads:[~2018-12-06 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1543481016-18500-1-git-send-email-firoz.khan@linaro.org>
[not found] ` <CALxhOnjSEp++W5T3Sf0eX+8hPt08ER22M817M-Vhd24_96a_EQ@mail.gmail.com>
[not found] ` <20181205063436.kzxgnvgexcgq572k@pburton-laptop>
2018-12-06 12:15 ` Maciej W. Rozycki
2018-12-06 16:19 ` Joseph Myers
2018-12-06 17:04 ` Maciej W. Rozycki
2018-12-06 17:20 ` Joseph Myers
2018-12-06 17:43 ` Maciej W. Rozycki [this message]
2018-12-06 18:11 ` Florian Weimer
2018-12-07 14:49 ` Maciej W. Rozycki
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=alpine.LFD.2.21.1812061729340.4294@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=firoz.khan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhogan@kernel.org \
--cc=joseph@codesourcery.com \
--cc=kstewart@linuxfoundation.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=paul.burton@mips.com \
--cc=pombredanne@nexb.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=y2038@lists.linaro.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).