Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: David Daney <ddaney@avtrex.com>
Cc: Kumba <kumba@gentoo.org>, linux-mips@linux-mips.org
Subject: Re: NPTL support for the kernel
Date: Mon, 21 Mar 2005 22:21:58 -0500	[thread overview]
Message-ID: <20050322032158.GA24188@nevyn.them.org> (raw)
In-Reply-To: <423F77DF.2060808@avtrex.com>

On Mon, Mar 21, 2005 at 05:41:51PM -0800, David Daney wrote:
> Kumba wrote:
> >Daniel Jacobowitz wrote:
> >
> >>
> >>Ping?
> >>
> >
> >Doesn't this need the glibc side of things to be effective?, or is it 
> >testable  w/o that component?

It is testable independently.  Also, I posted the glibc bits last week.

> I think the main point is that it should not break existing code.

Of course.  It doesn't.  The only thing it could possibly break would
be four-argument clone (it's supposed to be five argument, and the
missing argument conventionally goes in the middle... oops).  But
I strongly believe nothing is yet using the four-argument form so I
synced MIPS with the rest of the world.

> We need NPTL support in all three of GCC, Linux kernel and glibc before 
> it can be tested.  If it doesn't break existing code, I think it should 
> go in the kernel so that we have something on which to test gcc and glibc.

GCC support was committed two weeks ago, BTW.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

      reply	other threads:[~2005-03-22  3:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 14:11 NPTL support for the kernel Daniel Jacobowitz
2005-03-21 20:34 ` Daniel Jacobowitz
2005-03-22  1:21   ` Kumba
2005-03-22  1:41     ` David Daney
2005-03-22  3:21       ` Daniel Jacobowitz [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=20050322032158.GA24188@nevyn.them.org \
    --to=dan@debian.org \
    --cc=ddaney@avtrex.com \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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