From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2 8/9] i386: Move hypot implementation to C
Date: Mon, 1 Nov 2021 14:23:38 -0300 [thread overview]
Message-ID: <d0224f43-2e48-5522-21a5-1d5fd6c8279e@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110251709240.1572984@digraph.polyomino.org.uk>
On 25/10/2021 14:10, Joseph Myers wrote:
> On Mon, 25 Oct 2021, Adhemerval Zanella via Libc-alpha wrote:
>
>> + double r = math_narrow_eval (sqrtl (lx * lx + ly * ly));
>
> I'd expect math_narrow_eval to be called on the result cast to double, not
> on a value of long double type.
>
Ack.
next prev parent reply other threads:[~2021-11-01 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 11:57 [PATCH v2 0/9] Improve hypot() Adhemerval Zanella
2021-10-25 11:57 ` [PATCH v2 1/9] benchtests: Make hypot input random Adhemerval Zanella
2021-11-01 17:42 ` H.J. Lu
2021-10-25 11:57 ` [PATCH v2 2/9] benchtests: Add hypotf Adhemerval Zanella
2021-11-01 17:42 ` H.J. Lu
2021-10-25 11:57 ` [PATCH v2 3/9] math: Simplify hypotf implementation Adhemerval Zanella
2021-10-25 11:57 ` [PATCH v2 4/9] math: Use an improved algorithm for hypot (dbl-64) Adhemerval Zanella
2021-10-25 11:57 ` [PATCH v2 5/9] math: Use an improved algorithm for hypotl (ldbl-96) Adhemerval Zanella
2021-10-25 11:57 ` [PATCH v2 6/9] math: Use an improved algorithm for hypotl (ldbl-128) Adhemerval Zanella
2021-10-25 11:57 ` [PATCH v2 7/9] math: Remove powerpc e_hypot Adhemerval Zanella
2021-10-25 11:57 ` [PATCH v2 8/9] i386: Move hypot implementation to C Adhemerval Zanella
2021-10-25 17:10 ` Joseph Myers
2021-11-01 17:23 ` Adhemerval Zanella [this message]
2021-10-25 11:57 ` [PATCH v2 9/9] math: Remove the error handling wrapper from hypot and hypotf Adhemerval Zanella
2021-10-28 13:43 [PATCH v2 8/9] i386: Move hypot implementation to C Wilco Dijkstra
2021-11-01 17:09 ` Adhemerval Zanella
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=d0224f43-2e48-5522-21a5-1d5fd6c8279e@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).