From: Rich Felker <dalias@libc.org>
To: linux-sh@vger.kernel.org
Subject: Re: No newer system calls for SuperH64?
Date: Tue, 04 Feb 2020 14:23:58 +0000 [thread overview]
Message-ID: <20200204142358.GT1663@brightrain.aerifal.cx> (raw)
In-Reply-To: <939c9260-213f-cfd7-f81a-e9b635a6aa10@juszkiewicz.com.pl>
On Tue, Feb 04, 2020 at 03:13:23PM +0100, Marcin Juszkiewicz wrote:
> I am maintaining system calls table [1] which shows which system call
> has which number on all architectures supported by Linux kernel
> (including those removed in last years).
>
> 1. https://fedora.juszkiewicz.com.pl/syscalls.html
>
> Today I have noticed that SH64 supports system calls up to 393 which is
> pwritev2() one. None of later calls is supported in mainline 5.6-rc tree.
>
> Is it an error in kernel headers or it is true? Or maybe it is an error
> in my script but it works fine for other architectures.
>
> Note: I do not own nor plan to own SuperH64 hardware. I do not even
> remember where it was used. Just noticed weird state of it.
One reason you don't own it is that it essentially doesn't exist. :-)
GCC dropped SH64 support a few years ago because the arch essentially
never materialized and keeping it around was a lot of cruft. It should
be removed from the kernel too; I just haven't gotten around to
figuring out how to do that.
Rich
next prev parent reply other threads:[~2020-02-04 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 14:13 No newer system calls for SuperH64? Marcin Juszkiewicz
2020-02-04 14:23 ` Rich Felker [this message]
2020-02-04 17:05 ` Marcin Juszkiewicz
2020-02-06 18:08 ` Rob Landley
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=20200204142358.GT1663@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-sh@vger.kernel.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