From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: libc-ports@sourceware.org, Chris Metcalf <cmetcalf@tilera.com>,
Arnd Bergmann <arnd@arndb.de>,
linasvepstas@gmail.com, GLIBC Devel <libc-alpha@sourceware.org>,
linux-kernel@vger.kernel.org
Subject: Re: asm-generic/unistd.h and glibc use of NR_ipc
Date: Tue, 28 Sep 2010 16:52:47 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.64.1009281648040.22692@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201009281242.57006.vapier@gentoo.org>
On Tue, 28 Sep 2010, Mike Frysinger wrote:
> On Tuesday, September 28, 2010 09:05:13 Chris Metcalf wrote:
> > On 9/28/2010 4:40 AM, Arnd Bergmann wrote:
> > > Chris Metcalf is using the generic unistd.h file on the tile architecture
> > > and has a glibc port that should be easily portable to all future
> > > architectures. There are a few of them getting ready to be merged
> > > now (c6x, lm32, nios2, and some people have contacted me privately
> > > for architectures I cannot name).
>
> c6x lacks a MMU, so i dont see how it could possibly use glibc. same for
> lm32. nios2 at least has an optional MMU, so it'd be usable some of the time.
> so no, i dont see a generic unistd.h glibc port being useful for them.
A generic port would be useful for new architectures with MMU - but the
notion that "only rudimentary architecture support in glibc would be
needed" is mistaken. Note Chris's figures "another 30-odd files in
sysdeps/unix/sysv/linux/tile to implement the non-NPTL part of our glibc
support, plus 50-odd files in sysdeps/tile" - hardly rudimentary. Those
seem the right order of magnitude, if larger than the minimum; the Nios II
port currently has 59 new files in sysdeps directories, most of which I
expect would still be needed with the generic syscall ABI.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-09-28 16:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 23:26 Linas Vepstas
2010-09-28 0:02 ` Mike Frysinger
2010-09-28 8:40 ` Arnd Bergmann
2010-09-28 13:05 ` Chris Metcalf
2010-09-28 15:52 ` Joseph S. Myers
2010-09-28 16:13 ` Arnd Bergmann
2010-09-28 16:41 ` Joseph S. Myers
2010-09-28 20:08 ` Arnd Bergmann
2010-09-28 16:50 ` Mike Frysinger
2010-09-28 16:42 ` Mike Frysinger
2010-09-28 16:52 ` Joseph S. Myers [this message]
2010-09-28 17:36 ` Linas Vepstas
2010-09-30 13:23 ` Chris Metcalf
2010-09-29 5:16 ` Christoph Hellwig
2010-09-29 11:55 ` Arnd Bergmann
2011-03-10 16:46 ` Linas Vepstas
2011-03-10 17:07 ` Chris Metcalf
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=Pine.LNX.4.64.1009281648040.22692@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=arnd@arndb.de \
--cc=cmetcalf@tilera.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=linasvepstas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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
all inboxes | Powered by JetHome®