public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] math: Add math-use-builtins-fabs
Date: Mon, 4 Apr 2022 19:00:22 -0300	[thread overview]
Message-ID: <cfa04616-cc88-ea15-be94-ede63399aa3c@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2204042128400.326802@digraph.polyomino.org.uk>



On 04/04/2022 18:30, Joseph Myers wrote:
> On Mon, 4 Apr 2022, Adhemerval Zanella via Libc-alpha wrote:
> 
>> Both float and double are assumed to be supported (since generic
>> implementation uses it without a fallback), only long double and
>> float128 are defined.
> 
> The only case where built-in fabs (or copysign) may not work properly is 
> IBM long double in the soft-float case (see 
> sysdeps/powerpc/nofpu/Makefile).  I'd expect the default to be that it 
> works with an override for long double fabs in that one soft-float case.

I am adding a way to override float128 builtin support because I plan
to support building glibc with clang, which does not support inline
__builtin_fabsf128.  I change the patch to assume _Float128 support,
but set it on this patch makes the required further changes simpler.

> 
>> On ia64 it also fixes:
>>
>>   math/test-float64x-fabs
>>   math/test-ldouble-fabs
> 
> If this is fixing a bug that was user-visible in a release, there should 
> be a corresponding report in Bugzilla.
> 

Ack.

  reply	other threads:[~2022-04-04 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 20:58 Adhemerval Zanella
2022-04-04 21:30 ` Joseph Myers
2022-04-04 22:00   ` Adhemerval Zanella [this message]
2022-04-04 22:41     ` Joseph Myers
2022-04-05  1:55       ` Adhemerval Zanella
2022-04-05 11:50         ` Adhemerval Zanella
2022-04-05 15:53           ` Joseph Myers
2022-04-05 16:43             ` 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=cfa04616-cc88-ea15-be94-ede63399aa3c@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).