From: Ralf Baechle <ralf@oss.sgi.com>
To: Justin Carlson <carlson@sibyte.com>
Cc: Pete Popov <ppopov@mvista.com>,
"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: floating point on Nevada cpu
Date: Thu, 25 Jan 2001 09:37:43 -0800 [thread overview]
Message-ID: <20010125093743.A1288@bacchus.dhis.org> (raw)
On Wed, Jan 24, 2001 at 06:57:04PM -0800, Justin Carlson wrote:
> How are you compiling the code? And are you compiling it the same way on
> both platforms? Do you have fpu emulation enabled on a kernel that doesn't
> need it?
All MIPS FPUs need it; the architecture specification leaves it to the
implementor of a CPU which parts of the FP architecture are implemented
in hardware if at all; the missing parts have to be replaced in
software.
This piece of code shouldn't result in any FPU operations as printf is
very careful to avoid inaccuracies that might result from floating point
operations.
Ralf
next reply other threads:[~2001-01-25 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 17:37 Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=20010125093743.A1288@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=carlson@sibyte.com \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.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