From: "Gabriel F. T. Gomes" <gabriel@inconstante.eti.br>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
nd <nd@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 12/28] math: Use wordsize-64 version for isnan
Date: Wed, 12 Jun 2019 10:04:43 -0300 [thread overview]
Message-ID: <20190612130443.7iwfalrp7kdxqejw@tereshkova.br.ibm.com> (raw)
In-Reply-To: <VI1PR0801MB21274C177B4A5CA91A9AF87A83EC0@VI1PR0801MB2127.eurprd08.prod.outlook.com>
Hi, Adhemerval, Wilco,
On Wed, Jun 12 2019, Wilco Dijkstra wrote:
>
> > My take is math wordsize-64 was added to overcome some old compiler
> > deficiencies which most likely does not show any gain nowadays. Also,
> > specifically for isnan/isinf/isfinite I think multiple possible
> > optimization is a bit of over-engineering since the libc symbols will
> > be called with recent compiler only in very specific situations (most
> > likely not performance-wise).
>
> Yes we shouldn't worry about old compilers. There is no reason for so
> many duplicated implementations. Given modern compilers inline isinf etc,
> trying to save 1 instruction in GLIBC versions makes no sense.
Makes sense.
> > What I would like to do is just uses wordsize-64 implementations as
> > default one and aim to provide specialized WORDSIZE paths if it really
> > provides a real gain.
>
> Yes that is the best way forward. We should focus optimizations on
> areas where there is clear evidence of significant gains.
>
> > So for this specific usage, isnan/isinf/isfinite, do you agree we can
> > just use wordsize-64 as default?
>
> Absolutely.
Agreed.
Thank you both for all the clarification about 32-bits targets and
optimization focus.
next prev parent reply other threads:[~2019-06-12 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 17:15 [PATCH 12/28] math: Use wordsize-64 version for isnan Wilco Dijkstra
2019-06-11 21:04 ` Adhemerval Zanella
2019-06-12 11:11 ` Wilco Dijkstra
2019-06-12 13:04 ` Gabriel F. T. Gomes [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-29 13:35 [PATCH 00/28] powerpc floating-point optimization refactor Adhemerval Zanella
2019-03-29 13:35 ` [PATCH 12/28] math: Use wordsize-64 version for isnan Adhemerval Zanella
2019-06-05 22:45 ` Gabriel F. T. Gomes
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190612130443.7iwfalrp7kdxqejw@tereshkova.br.ibm.com \
--to=gabriel@inconstante.eti.br \
--cc=Wilco.Dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).