From: Geoffrey KEATING <geoffk@discus.anu.edu.au>
To: David Edelsohn <dje@watson.ibm.com>
Cc: hjl@lucon.org (H.J. Lu),
zack@rabi.phys.columbia.edu (Zack Weinberg),
egcs@cygnus.com, libc-linux@gnu.org (GNU C Library)
Subject: Re: A patch for libm-ieee754
Date: Sun, 22 Feb 1998 19:30:00 -0000 [thread overview]
Message-ID: <199802230329.OAA14490@discus.anu.edu.au> (raw)
In-Reply-To: <9802230237.AA33074@rios1.watson.ibm.com>
> Date: Sun, 22 Feb 1998 21:37:55 -0500
> From: David Edelsohn <dje@watson.ibm.com>
> On PowerPC you probably also need -mno-fused-madd option to
> disable use of the fma, etc. instructions because of the intermediate
> extended precision. Note that this will halve FP performance in some
> cases.
This is not necessary.
The libm doesn't mind if _expressions_ have extra precision, the
important thing is that _variables_ have the right precision.
In the same way, I expect
unsigned char x;
unsigned char y=0xff, z = 1;
x = y + z;
assert(x == 0);
to have the assertion succeed; I don't expect the compiler to decide
"you said 'unsigned char', but it'll actually behave like an 'unsigned
int'".
[I hope that gcc won't combine
double x,y,z,r;
r = x*y;
r = r+z;
into a fused multiply-add!]
Besides, I test these routines on PPC, and I make sure they do the
right thing :-). I don't think anyone had tried running them on x86
before, because the 387 FPU has most of these routines in hardware.
--
Geoff Keating <Geoff.Keating@anu.edu.au>
prev parent reply other threads:[~1998-02-22 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802220053.TAA29191@rabi.phys.columbia.edu>
1998-02-21 17:50 ` Who is fixing libm-ieee754? H.J. Lu
1998-02-21 18:55 ` A patch for libm-ieee754 H.J. Lu
1998-02-22 7:42 ` Andreas Jaeger
1998-02-22 13:03 ` Toon Moene
1998-02-22 13:33 ` Ulrich Drepper
1998-02-22 13:42 ` Andreas Jaeger
1998-02-22 18:18 ` Geoffrey KEATING
1998-02-22 18:39 ` David Edelsohn
1998-02-22 19:30 ` Geoffrey KEATING [this message]
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=199802230329.OAA14490@discus.anu.edu.au \
--to=geoffk@discus.anu.edu.au \
--cc=dje@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=libc-linux@gnu.org \
--cc=zack@rabi.phys.columbia.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).