(OT) floating-point numbers

[Mantorok Redgormor]

What have some of you guys read to have a solid understanding of how
floating-point numbers are represented or handled by the processor and
what the difference between single and double precision is?

I found this: http://docs.sun.com/source/806-3568/ncg_goldberg.html

Not sure if this is what I should be reading? Maybe a more authoritive
document exists?

[Glen Herrmannsfeldt]

"Mantorok Redgormor" <ne*****@tokyo.com> wrote in message
news:41**************************@posting.google.c om...

What have some of you guys read to have a solid understanding of how
floating-point numbers are represented or handled by the processor and
what the difference between single and double precision is?

I found this: http://docs.sun.com/source/806-3568/ncg_goldberg.html

Not sure if this is what I should be reading? Maybe a more authoritive
document exists?

Kahan's "What every computer scientist should know about floating point" is
probably a good start.

-- glen

[Randy Howard]

In article <sKT9b.484801$uu5.83261@sccrnsc04>, ga*@ugcs.caltech.edu
says...

"Mantorok Redgormor" <ne*****@tokyo.com> wrote in message
news:41**************************@posting.google.c om...

What have some of you guys read to have a solid understanding of how
floating-point numbers are represented or handled by the processor and
what the difference between single and double precision is?

I found this: http://docs.sun.com/source/806-3568/ncg_goldberg.html

Not sure if this is what I should be reading? Maybe a more authoritive
document exists?

Kahan's "What every computer scientist should know about floating point" is
probably a good start.

Actually, the above link is to that article (actually a reprint of it),
but it was written by David Goldberg, not Kahan.

Perhaps you were thinking of his "How JAVA's Floating-Point Hurts Everyone
Everywhere" instead?

--
Randy Howard _o
2reply remove FOOBAR \<,
______________________()/ ()______________________________________________
SCO Spam-magnet: po********@sco.com

[Glen Herrmannsfeldt]

"Randy Howard" <ra**********@FOOmegapathdslBAR.net> wrote in message
news:MP************************@news.megapathdsl.n et...

In article <sKT9b.484801$uu5.83261@sccrnsc04>, ga*@ugcs.caltech.edu
says...

"Mantorok Redgormor" <ne*****@tokyo.com> wrote in message
news:41**************************@posting.google.c om...

What have some of you guys read to have a solid understanding of how
floating-point numbers are represented or handled by the processor and
what the difference between single and double precision is?

I found this: http://docs.sun.com/source/806-3568/ncg_goldberg.html

Not sure if this is what I should be reading? Maybe a more authoritive
document exists?

Kahan's "What every computer scientist should know about floating point" is probably a good start.

Actually, the above link is to that article (actually a reprint of it),
but it was written by David Goldberg, not Kahan.

Perhaps you were thinking of his "How JAVA's Floating-Point Hurts Everyone
Everywhere" instead?

Well, first, please forgive me for the mistake in authorship.

It seems that there is some connection between that paper and Kahan, but
yes, he didn't write it.

So then I had to go and read "How JAVA's Floating-Point Hurts Everyone
Everywhere" to find out. (Also, note that this paper includes much more
than Java's floating point in its examples.)

I believe it is a different paper than I was remembering, but it includes
results from many of Kahan's papers.

Among those are the effects of doing floating point arithmetic in higher
precision than specified.

To get back to discussing C, the paper comments that the original K&R C
would promote float variables to double before all calculations, where ANSI
C allows calculations on float variables to be done in float precision. He
considers that a mistake.

So, I would say that both are good reading materials for users of floating
point arithmetic.

-- glen