From: Richard Allen <rsaxvc@rsaxvc.net>
To: newlib@sourceware.org
Subject: [PATCH] Avoid extra float->double conversion
Date: Wed, 19 Apr 2017 23:53:00 -0000 [thread overview]
Message-ID: <CAMY0PLVpmE2_5WL2jZLq8M=Zv-EE6f7u8VE0hy1gX4T7vCYvSw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 100 bytes --]
Patch avoids an unnecessary float->double
conversion to save a small amount of codespace.
-Richard
[-- Attachment #2: 0002-Convert-rint-to-rintf.patch --]
[-- Type: text/x-patch, Size: 1109 bytes --]
From 2369a552cf62dfb53f14978587a338072f6abd2c Mon Sep 17 00:00:00 2001
From: Richard <rsaxvc@rsaxvc.net>
Date: Wed, 19 Apr 2017 18:37:17 -0500
Subject: [PATCH 2/2] Convert rint() to rintf()
This was causing an unnecessary increase
in precision, as well as additional function
calls to do float->double conversion on
platforms with only a single-precision FPU.
---
newlib/libm/math/wf_pow.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/newlib/libm/math/wf_pow.c b/newlib/libm/math/wf_pow.c
index bd9de0ad0..5b79dd151 100644
--- a/newlib/libm/math/wf_pow.c
+++ b/newlib/libm/math/wf_pow.c
@@ -126,11 +126,11 @@
if (_LIB_VERSION == _SVID_) {
exc.retval = HUGE;
y *= 0.5;
- if(x<0.0&&rint(y)!=y) exc.retval = -HUGE;
+ if(x<0.0&&rintf(y)!=y) exc.retval = -HUGE;
} else {
exc.retval = HUGE_VAL;
y *= 0.5;
- if(x<0.0&&rint(y)!=y) exc.retval = -HUGE_VAL;
+ if(x<0.0&&rintf(y)!=y) exc.retval = -HUGE_VAL;
}
if (_LIB_VERSION == _POSIX_)
errno = ERANGE;
--
2.11.0
next reply other threads:[~2017-04-19 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 23:53 Richard Allen [this message]
2017-04-20 0:03 ` Richard Allen
2017-04-20 0:36 ` Craig Howland
2017-04-21 13:30 ` Richard Allen
2017-05-18 23:58 ` Richard Allen
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='CAMY0PLVpmE2_5WL2jZLq8M=Zv-EE6f7u8VE0hy1gX4T7vCYvSw@mail.gmail.com' \
--to=rsaxvc@rsaxvc.net \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).