public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: libc-ports@sourceware.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	Chris Metcalf <cmetcalf@tilera.com>,
	linasvepstas@gmail.com, linux-kernel@vger.kernel.org,
	andrew@codesourcery.com
Subject: Re: asm-generic/unistd.h and glibc use of NR_ipc
Date: Tue, 28 Sep 2010 12:50:45 -0400	[thread overview]
Message-ID: <201009281250.47196.vapier@gentoo.org> (raw)
In-Reply-To: <201009281813.56443.arnd@arndb.de>

[-- Attachment #1: Type: Text/Plain, Size: 1090 bytes --]

On Tuesday, September 28, 2010 12:13:56 Arnd Bergmann wrote:
> On Tuesday 28 September 2010, Joseph S. Myers wrote:
> > C6X has no MMU so a glibc port isn't a possibility.  There are indeed
> > uClibc and GCC ports we will be contributing in due course - but the
> > linker support for shared objects is still in development (I contributed
> > the static linking binutils support upstream earlier this year) and is
> > required for building anything for uClinux userspace for this platform.
> 
> Right. Obviously the same question exists for uClibc though: The C6X
> syscall ABI will need to be rewritten (as in deleted and replaced by
> generic code) in the kernel in order to get merged, so the uClibc port
> will have to gain the same kind of generic API that we need for glibc.

i dont think uClibc needs nearly as much work as glibc.  it already goes out 
of its way to avoid code duplication whenever possible (and then some).  the 
position glibc takes wrt copy & paste at the file level makes me ill and so i 
tend to double down in my uClibc efforts there.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2010-09-28 16:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 23:26 asm-generic/unistd.h and glibc use of NR_ipc 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 [this message]
2010-09-28 16:42     ` Mike Frysinger
2010-09-28 16:52       ` Joseph S. Myers
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=201009281250.47196.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=andrew@codesourcery.com \
    --cc=arnd@arndb.de \
    --cc=cmetcalf@tilera.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=linasvepstas@gmail.com \
    --cc=linux-kernel@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