Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Zhang Fuxin <fxzhang@ict.ac.cn>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Re: pthread support in mipsel-linux
Date: Fri, 22 Feb 2002 22:11:28 -0800	[thread overview]
Message-ID: <20020222221128.A28938@lucon.org> (raw)
In-Reply-To: <200202230415.g1N4FI930898@oss.sgi.com>; from fxzhang@ict.ac.cn on Sat, Feb 23, 2002 at 11:12:06AM +0800

On Sat, Feb 23, 2002 at 11:12:06AM +0800, Zhang Fuxin wrote:
> hi,
> 
> >
> >Mutex is now implemented with spin lock by default. BTW, how many
> >people have run "make check" on glibc compiled -mips1?
> I did with glibc-2.2.4 natively compiled,no failure till libm-test

The linuxthreads test comes after math.

> (i configured it by default,then it used -mips1?)
> 

Yes. BTW, I found the ll/sc bug by doing "make check" on gcc 3.1 in
CVS.


H.J.

      reply	other threads:[~2002-02-23  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  3:12 Re: pthread support in mipsel-linux Zhang Fuxin
2002-02-23  6:11 ` H . J . Lu [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=20020222221128.A28938@lucon.org \
    --to=hjl@lucon.org \
    --cc=fxzhang@ict.ac.cn \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox