From: Andoni Arregi <andoni.arregui@gtd-gmbh.de>
To: newlib@sourceware.org
Subject: [PATCH 0/2] Fix lgammaf and lgamma for small ranges and in [2, 3[
Date: Thu, 10 Feb 2022 17:07:32 +0100 [thread overview]
Message-ID: <76d19bdcc9b3c685a33ce27bddefeeafc5001294.camel@gtd-gmbh.de> (raw)
In-Reply-To: <YgUn/f7micaqjfiR@calimero.vinschen.de>
lgammaf shows a wrong behavior for very small cases and also for cases
in the range [2.0, 3.0), this last problem also being present in
lgamma. These wrong behaviors also affect the tgammaf and tgamma
functions respectively. The provided patches fix these errors.
Andoni Arregi (2):
Improve lgammaf range for very small cases
Add a missing default case in lgamma
newlib/libm/math/er_lgamma.c | 1 +
newlib/libm/math/erf_lgamma.c | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
--
2.35.1
next prev parent reply other threads:[~2022-02-10 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 6:38 regression in Newlib 4.2.0 (lgammaf) Paul Zimmermann
2022-02-09 16:28 ` [PATCH 1/2] Improve lgammaf range for very small cases Andoni Arregi
2022-02-10 14:58 ` Corinna Vinschen
2022-02-10 16:07 ` Andoni Arregi [this message]
2022-02-10 16:10 ` Andoni Arregi
2022-02-10 16:21 ` Paul Zimmermann
2022-02-10 16:12 ` [PATCH 2/2] Add a missing default case in lgamma Andoni Arregi
2022-02-10 17:29 ` Paul Zimmermann
2022-02-11 11:14 ` Andoni Arregi
2022-02-10 16:16 ` [PATCH 1/2] Improve lgammaf range for very small cases Andoni Arregi
2022-02-11 11:19 ` Andoni Arregi
2022-02-09 16:30 ` [PATCH 2/2] Add a missing default case in lgamma Andoni Arregi
2022-02-09 16:49 ` regression in Newlib 4.2.0 (lgammaf) Andoni Arregi
2022-02-11 11:16 ` [PATCH] Improve lgammaf range for very small cases Andoni Arregi
2022-02-14 13:46 ` Corinna Vinschen
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=76d19bdcc9b3c685a33ce27bddefeeafc5001294.camel@gtd-gmbh.de \
--to=andoni.arregui@gtd-gmbh.de \
--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).