From: Joseph Myers <joseph@codesourcery.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: FX <fxcoudert@gmail.com>, <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Add __builtin_iseqsig()
Date: Mon, 31 Oct 2022 18:24:13 +0000 [thread overview]
Message-ID: <46e27067-6cb9-a5fc-f96-394515bcf9d@codesourcery.com> (raw)
In-Reply-To: <fce4f148-b2ca-7b74-1b67-8d70e19dd891@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]
On Fri, 28 Oct 2022, Jeff Law via Gcc-patches wrote:
> Joseph, do you have bits in this space that are going to be landing soon, or
> is your C2X work focused elsewhere? Are there other C2X routines we need to
> be proving builtins for?
I don't have any builtins work planned for GCC 13 (maybe adjustments to
__builtin_tgmath semantics to match changes in C2X, but that's a keyword,
not a built-in function).
See <https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603012.html>
for my comments on (the tests in) this patch.
Lots of <math.h> functions could sensibly have built-in versions, whether
for inline expansion, optimization for constant arguments or both. Note
that for those added from TS 18661-4, it will be more convenient to add
glibc support once MPFR 4.2 is out so that gen-auto-libm-tests doesn't
depend on an unreleased MPFR version, and likewise MPFR 4.2 will be needed
for optimizing those functions for constant arguments. But other
highlights for which built-in functions might make sense in some cases
include: issubnormal, iszero (see bugs 77925 / 77926, where Tamar
Christina's patch needed to be reverted); probably the fromfp functions
(but note that the interface in C2X is different from that in TS 18661-1
and I haven't yet implemented those changes in glibc); the functions that
round their result to a narrower type (supported as hardware operations on
current POWER, I think); the functions bound to new maximum / minimum
operations from IEEEE 754-2019 (some of which are supported by RISC-V
instructions). Also the <stdbit.h> functions; I expect to implement those
for glibc largely using existing built-in functions, but more direct
built-in function support for the <stdbit.h> names may make sense.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-10-31 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 21:02 FX
2022-09-09 17:55 ` FX
2022-09-21 9:40 ` FX
2022-10-06 8:40 ` FX
2022-10-06 21:46 ` Joseph Myers
2023-06-06 18:15 ` FX Coudert
2023-06-13 16:49 ` FX Coudert
2023-06-26 8:59 ` FX Coudert
2023-07-12 9:39 ` FX Coudert
2023-07-19 14:48 ` FX Coudert
2023-07-20 7:17 ` Richard Biener
2022-10-29 5:10 ` Jeff Law
2022-10-31 18:24 ` Joseph Myers [this message]
2022-10-31 19:15 ` FX
2022-10-31 22:35 ` Joseph Myers
2022-11-20 17:10 ` Jeff Law
2022-11-20 17:28 ` FX
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=46e27067-6cb9-a5fc-f96-394515bcf9d@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.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).