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 11:58:29 -0700 [thread overview]
Message-ID: <3B1542D5.7D74C295@mvista.com> (raw)
In-Reply-To: Pine.SGI.4.33.0105301431160.11351-100000@thor.tetracon-eng.net
"J. Scott Kasten" wrote:
>
> On Wed, 30 May 2001, Jun Sun wrote:
>
> > "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.
>
> If I recall correctly, that was S0 not being preserved under certain
> system calls. Which I have taken care of.
>
> >
> > Yes, it runs fine on my machines.
> >
> > Jun
> >
>
> When you say runs fine, do you mean the 2.0.x, the 2.2.x or both?
>
> Thanks for your response.
Both. There are some bug fixes needed to the get the new glibc 2.2.x
working. Once the fixes are settled, we will post them.
Jun
next prev parent reply other threads:[~2001-05-30 19:38 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 ` Pthreads Jun Sun
2001-05-30 18:34 ` Pthreads J. Scott Kasten
2001-05-30 18:34 ` Pthreads J. Scott Kasten
2001-05-30 18:58 ` Jun Sun [this message]
-- 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=3B1542D5.7D74C295@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.