From: Pete Popov <ppopov@mvista.com>
To: Steve Johnson <stevej@ridgerun.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: floating point on Nevada cpu
Date: Thu, 25 Jan 2001 10:02:10 -0800 [thread overview]
Message-ID: <3A706A22.6B760617@mvista.com> (raw)
In-Reply-To: 3A703E3C.360FB4FF@ridgerun.com
Steve,
Steve Johnson wrote:
>
> Pete,
>
> We had a problem in user-space apps all showing 0 for floating-point
> results because we hadn't set the ST0_FR bit to 0, and we had a mis-match
> between user libraries (MIPS3k-compatible) and the floating point registers.
> We noticed the problem when we couldn't run "ps" or "rm" correctly and tracked
> it down from some old postings by Ralf and friends. Maybe this is your
> problem, too?
>
> I added this to our setup call:
>
> set_cp0_status(ST0_FR, 0);
Problem solved before I finished my first cup of coffee. Thanks!
I bet this problem will show up here and there depending on how the boot
code sets cp0. Seems like adding the above line in a mips generic init
routine would be a good thing.
Pete
next prev parent reply other threads:[~2001-01-25 18:02 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
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 [this message]
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=3A706A22.6B760617@mvista.com \
--to=ppopov@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=stevej@ridgerun.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.