From: Keith Packard <keithp@keithp.com>
To: Corinna Vinschen <vinschen@redhat.com>
Cc: Kito Cheng <kito.cheng@sifive.com>,
newlib@sourceware.org, kito.cheng@gmail.com,
Aldy Hernandez <aldyh@redhat.com>,
Andrew MacLeod <amacleod@redhat.com>
Subject: Re: [PATCH] libm: Fixing overflow handling issue for scalbnf and scalbn
Date: Wed, 21 Jul 2021 16:33:59 -0700 [thread overview]
Message-ID: <87y29znswo.fsf@keithp.com> (raw)
In-Reply-To: <YPfT8BlAygKzhC6t@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Corinna Vinschen <vinschen@redhat.com> writes:
> Thanks for verifying. PUshed.
I just finished running more extensive tests that validates about 400
configurations of the library; scalbn and scalbnf aren't setting errno
when the library is built in non-IEEE mode.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2021-07-21 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 8:50 Kito Cheng
2021-07-20 16:12 ` Keith Packard
2021-07-21 7:59 ` Corinna Vinschen
2021-07-21 23:33 ` Keith Packard [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=87y29znswo.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=aldyh@redhat.com \
--cc=amacleod@redhat.com \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=newlib@sourceware.org \
--cc=vinschen@redhat.com \
/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).