| To: | Pete Popov <ppopov@mvista.com> |
|---|---|
| Subject: | Re: floating point on Nevada cpu |
| From: | Steve Johnson <stevej@ridgerun.com> |
| Date: | Thu, 25 Jan 2001 07:54:53 -0700 |
| Cc: | "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com> |
| Organization: | Ridgerun, Inc. |
| References: | <3A6F8F66.6258801@mvista.com> <0101241833281Q.00834@plugh.sibyte.com> <3A6F9814.3E39027@mvista.com> <0101241917341S.00834@plugh.sibyte.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
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);
Steve
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Linux/MIPS installation (FAQ? HOWTO?), Guido Guenther |
|---|---|
| Next by Date: | [FIX] sysmips(MIPS_ATMIC_SET, ...) ret_from_sys_call vs. o32_ret_from_sys_call, Florian Lohoff |
| Previous by Thread: | Re: floating point on Nevada cpu, Justin Carlson |
| Next by Thread: | Re: floating point on Nevada cpu, Pete Popov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
