Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Carsten Langgaard <carstenl@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: FPU test on RedHat7.1
Date: Thu, 22 Nov 2001 10:39:30 -0800	[thread overview]
Message-ID: <20011122103930.A2007@lucon.org> (raw)
In-Reply-To: <3BFD1BA7.C4490465@mips.com>; from carstenl@mips.com on Thu, Nov 22, 2001 at 04:37:11PM +0100

On Thu, Nov 22, 2001 at 04:37:11PM +0100, Carsten Langgaard wrote:
> The attached tests fails on my RedHat7.1 system, but works fine on my
> old HardHat5.1.
> Anyone got any idea.
> 
> compile:
> g++ -o fpu_test fpu_test.cc
> 

Many FPU related tests in the current glibc from CVS failed on MIPS. I
am planning to look into them. But I need to find time and docs on MIPS
FPU.


H.J.

  reply	other threads:[~2001-11-22 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 15:37 FPU test on RedHat7.1 Carsten Langgaard
2001-11-22 18:39 ` H . J . Lu [this message]
2001-11-23 14:54   ` Carsten Langgaard
2001-11-24 19:25     ` H . J . Lu
2001-11-26  9:22       ` Carsten Langgaard

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=20011122103930.A2007@lucon.org \
    --to=hjl@lucon.org \
    --cc=carstenl@mips.com \
    --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