From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH] math: Add math-use-builtins-fabs
Date: Mon, 4 Apr 2022 22:41:48 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2204042239000.326802@digraph.polyomino.org.uk> (raw)
In-Reply-To: <cfa04616-cc88-ea15-be94-ede63399aa3c@linaro.org>
On Mon, 4 Apr 2022, Adhemerval Zanella via Libc-alpha wrote:
> to support building glibc with clang, which does not support inline
> __builtin_fabsf128. I change the patch to assume _Float128 support,
And also not under another name (cf. how sysdeps/x86/bits/floatn.h uses
__builtin_fabsq before GCC 7)?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-04-04 22:41 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
2022-04-04 22:41 ` Joseph Myers [this message]
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=alpine.DEB.2.22.394.2204042239000.326802@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--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).