Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Jim Gifford <maillist@jg555.com>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: MIPS64 NPTL Status
Date: Thu, 22 Sep 2005 17:30:20 -0400	[thread overview]
Message-ID: <20050922213020.GA15905@nevyn.them.org> (raw)
In-Reply-To: <43323D35.9030905@jg555.com>

On Wed, Sep 21, 2005 at 10:12:21PM -0700, Jim Gifford wrote:
> Looking through the latest glibc snapshot they have removed linuxthreads 
> and moved it to ports. I know Daniel has been working on getting NPTL to 
> work on MIPS32, which it does. Thank you Daniel. I know from emails I 
> read around linux-mips.org he was going to work on MIPS64 NPTL, just 
> curious to the status.
> 
> For the record the current glibc snapshot will not build at all under 
> MIPS64. Here is the error message I have received, still working on 
> getting it to build properly

Hi Jim,

I've got complete patches to do this.  I thought I'd already submitted
them, but I found out yesterday morning that I hadn't... simply an
accident.  I've posted my complete set of glibc patches here:

http://return.false.org/~drow/mips/glibc-2005-09-22-HEAD-MIPS64-NPTL.tar.gz

As of this morning, they work for me, using GCC HEAD and binutils HEAD.
Rather more work is required for GDB (see my earlier post today and the
last patch in the above tarball).

There are some test failures.  IIRC, at least one of them is a GCC
unwinder bug that I haven't dug out the fix for yet from my archives.
I'm going to try to get all of this merged soon.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  parent reply	other threads:[~2005-09-22 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22  5:12 MIPS64 NPTL Status Jim Gifford
2005-09-22 20:38 ` John Connett
2005-09-22 20:44   ` Michael Uhler
2005-09-22 21:30 ` Daniel Jacobowitz [this message]
2005-09-22 22:28   ` Jim Gifford
2005-09-22 22:30     ` Daniel Jacobowitz
2005-09-26 15:17     ` Jim Gifford
2005-09-27 13:09       ` Daniel Jacobowitz

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=20050922213020.GA15905@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@linux-mips.org \
    --cc=maillist@jg555.com \
    /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