All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: "J. Scott Kasten" <jsk@tetracon-eng.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: Pthreads.
Date: Wed, 30 May 2001 10:30:57 -0700	[thread overview]
Message-ID: <3B152E51.ACF145BE@mvista.com> (raw)
In-Reply-To: Pine.SGI.4.33.0105301100150.8607-100000@thor.tetracon-eng.net

"J. Scott Kasten" wrote:
> 
> If I recall correctly, some time ago, Jun Sun was looking at pthreads.
> What is the status of threads in glibc-2.0.6/.7 and glibc-2.2.x for mips?
> I.E. works, broken, how bad, to do???
> 

I found a bug in the kernel that causes register corruption, which causes
pthread to fail.  The bug has been fixed for a while in the CVS tree.  I don't
recall any glibc specific patches.  

Yes, it runs fine on my machines.

Jun

  reply	other threads:[~2001-05-30 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 15:02 Pthreads J. Scott Kasten
2001-05-30 15:02 ` Pthreads J. Scott Kasten
2001-05-30 17:30 ` Jun Sun [this message]
2001-05-30 18:34   ` Pthreads J. Scott Kasten
2001-05-30 18:34     ` Pthreads J. Scott Kasten
2001-05-30 18:58     ` Pthreads Jun Sun
  -- strict thread matches above, loose matches on Subject: below --
1998-07-17 17:40 Pthreads ralf

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=3B152E51.ACF145BE@mvista.com \
    --to=jsun@mvista.com \
    --cc=jsk@tetracon-eng.net \
    --cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.