From: Jeff Johnston <jjohnstn@redhat.com>
To: Keith Packard <keithp@keithp.com>
Cc: Paul Zimmermann <Paul.Zimmermann@inria.fr>,
Newlib <newlib@sourceware.org>
Subject: Re: regression in tgamma?
Date: Thu, 17 Dec 2020 16:28:12 -0500 [thread overview]
Message-ID: <CAOox84uKYDq7huWPwFFz7jZpJpUR1dJdfQipv-tr1RU6YzxESg@mail.gmail.com> (raw)
In-Reply-To: <87v9d05jkl.fsf@keithp.com>
Thanks Keith,
I have modified er_lgamma.c, erf_lgamma.c, w_tgamma.c, wf_tgamma.c based on
code changes in picolibc.
I did not add the new ___ieee754_ sub-functions and instead modified the
existing code assuming that the function
was called with *signgam = 0. We can always do a merge from picolibc in
the future.
With the new code, the test runs as expected.
Paul, please confirm before tomorrow.
Thanks,
-- Jeff J.
On Thu, Dec 17, 2020 at 2:17 PM Keith Packard <keithp@keithp.com> wrote:
> Jeff Johnston <jjohnstn@redhat.com> writes:
>
> > I am also seeing inf instead of -inf for both tgamma and tgammaf in my
> > testing.
>
> Yeah, looks like there are quite a few fixes in picolibc that I haven't
> had time to send over to newlib.
>
> I've also fixed a bunch of exception problems when compiling with clang,
> which is happy to evaluate expressions known at compile time, even
> though that doesn't generate exceptions at runtime. (things like 'return
> one/zero;')
>
> I've also generated tests for return values, exceptions and errnos for
> the math functions to make sure they match the relevant specs and also
> match glibc (mostly as a way to check the tests).
>
> Anyone is welcome to pull those fixes out of picolibc and get them into
> newlib; I probably won't have time for a while.
>
> --
> -keith
>
next prev parent reply other threads:[~2020-12-17 21:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 13:48 Paul Zimmermann
2020-12-16 20:31 ` Jeff Johnston
2020-12-17 7:29 ` Paul Zimmermann
2020-12-17 16:13 ` Keith Packard
2020-12-17 18:27 ` Jeff Johnston
2020-12-17 19:16 ` Keith Packard
2020-12-17 21:28 ` Jeff Johnston [this message]
2020-12-18 6:36 ` Paul Zimmermann
2020-12-18 8:42 ` Corinna Vinschen
2020-12-18 8:54 ` Paul Zimmermann
2020-12-18 9:07 ` Corinna Vinschen
2020-12-18 17:42 ` Jeff Johnston
2020-12-18 8:37 ` Paul Zimmermann
-- strict thread matches above, loose matches on Subject: below --
2020-12-15 13:35 Paul Zimmermann
2020-12-15 17:11 ` Jeff Johnston
2020-12-16 6:36 ` Paul Zimmermann
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=CAOox84uKYDq7huWPwFFz7jZpJpUR1dJdfQipv-tr1RU6YzxESg@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=Paul.Zimmermann@inria.fr \
--cc=keithp@keithp.com \
--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).