From: Jason Riedy <ejr@CS.Berkeley.EDU>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: changing precision control setting in initial FPU context
Date: Sat, 03 Mar 2001 20:21:56 -0800 [thread overview]
Message-ID: <200103040421.UAA28916@lotus.CS.Berkeley.EDU> (raw)
In-Reply-To: Your message of "03 Mar 2001 17:17:47 CST." <vbar90eqw6c.fsf@mozart.stat.wisc.edu>
And Kevin Buhr writes:
-
- > What Linux does presently on x86 is as right as right can be on
- > this platform.
-
- I'm not so sure.
Let me rephrase: According to a designer of the x87 and one
of the IEEE 754 authors, the behavior currently in Linux and
glibc is reasonable on x86. Reasonable is the best you can
hope for in floating-point.
Double-rounding from intermediate spills isn't reasonable, but
that's neither a kernel nor a C library issue. Tackling that
issue in the compiler is difficult. MS punted and gcc's trying
to get things right (or has, I've lost track, search for `XF',
`mode', and `spill' in the archives). If you want plain single-
or double-precision arithmetic, use a recent IA-32 with SSE2
instructions.
What I should have done in my first response was to refer you to
Doug Priest's supplement to David Goldberg's ``What Every Computer
Scientist Should Know about Floating-Point Arithmetic''. Of course,
you need first read the paper itself. You can find a copy at
http://www.validgh.com/
Read it with paper, pencil, and calculator handy. You'll want to
work out some examples for yourself. The supplement covers the
issues well.
If you really want to get upset at operating systems, complain
about their lack of support for efficient floating-point exception
handling. ;) (Or search for wmexcp, which will kill that
complaint on x86 Linux.)
Jason
next prev parent reply other threads:[~2001-03-04 4:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-03 7:12 RFC: changing precision control setting in initial FPU context Kevin Buhr
2001-03-03 9:31 ` Albert D. Cahalan
2001-03-03 10:26 ` Kevin Buhr
2001-03-03 20:04 ` Albert D. Cahalan
2001-03-03 21:00 ` Jason Riedy
2001-03-03 23:17 ` Kevin Buhr
2001-03-04 4:21 ` Jason Riedy [this message]
2001-03-03 22:34 ` Kevin Buhr
2001-03-03 10:47 Adam J. Richter
2001-03-03 23:29 ` Kevin Buhr
2001-03-03 23:37 ` Alan Cox
2001-03-04 0:27 ` Kevin Buhr
2001-03-04 0:45 ` Ulrich Drepper
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=200103040421.UAA28916@lotus.CS.Berkeley.EDU \
--to=ejr@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).