Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@mvista.com>
To: carlson@sibyte.com
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: floating point on Nevada cpu
Date: Wed, 24 Jan 2001 18:52:16 -0800	[thread overview]
Message-ID: <3A6F94E0.4AB07CEB@mvista.com> (raw)
In-Reply-To: 0101241833281Q.00834@plugh.sibyte.com

Justin Carlson wrote:
> 
> On Wed, 24 Jan 2001, Pete Popov wrote:
> > This simple test fails on a Nevada (5231) cpu:
> >
> > int main()
> > {
> >     float x1,x2,x3;
> >
> >     x1 = 7.5;
> >     x2 = 2.0;
> >     x3 = x1/x2;
> >     printf("x3 = %f\n", x3);
> > }
> >
> 
> Ummm...care to tell *how* it fails?

Here it is:

sh-2.03# ./fl
x3 = 0.000000


I'm running a test9 based kernel, but the same kernel compiled for my
Indigo2 produces the right result.  Also, the uptime commands complains
with:


Unknown HZ value! (2147483647) Assume 100.


At the console, I get "Setting flush to zero for uptime."  So, I took a
look at arch/mips/kernel/traps.c and the kernel retries the instruction
with denormalized instructions flushed to zero. However, the 5200
signals an unimplemented operation even if the FS bit is set. 

In any case, the first simple test doesn't run into the "flush to zero"
problem but the result is still bad.

Pete

  reply	other threads:[~2001-01-25  2:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25  2:28 floating point on Nevada cpu Pete Popov
2001-01-25  2:33 ` Justin Carlson
2001-01-25  2:52   ` Pete Popov [this message]
2001-01-25  2:57     ` Justin Carlson
2001-01-25  2:57       ` Justin Carlson
2001-01-25  3:05   ` Pete Popov
2001-01-25  3:16     ` Justin Carlson
2001-01-25 14:54       ` Steve Johnson
2001-01-25 18:02         ` Pete Popov
2001-01-26 10:14           ` Kevin D. Kissell
2001-01-26 10:14             ` Kevin D. Kissell
2001-01-26 13:01             ` Steve Johnson
2001-01-26 13:57               ` Kevin D. Kissell
2001-01-26 13:57                 ` Kevin D. Kissell
2001-01-27 19:16             ` Ralf Baechle
2001-01-27 19:16               ` Ralf Baechle
2001-01-25 17:26       ` Ralf Baechle
2001-01-25 20:01         ` Justin Carlson
2001-01-25 22:12 ` Ralf Baechle
2001-01-26  7:53   ` Carsten Langgaard
  -- strict thread matches above, loose matches on Subject: below --
2001-01-25 17:37 Ralf Baechle

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=3A6F94E0.4AB07CEB@mvista.com \
    --to=ppopov@mvista.com \
    --cc=carlson@sibyte.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