From: Jeff Law <jeffreyalaw@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [PATCH] builtins: Add __builtin_nextafterf16b builtin
Date: Mon, 24 Oct 2022 09:24:53 -0600 [thread overview]
Message-ID: <28635ee5-0ff0-aeaa-0f8d-4c31d2e05159@gmail.com> (raw)
In-Reply-To: <Y1JI5QFI4PPKRDJk@tucnak>
On 10/21/22 01:23, Jakub Jelinek wrote:
> Hi!
>
> On top of the pending
> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603665.html
> patch, the following patch adds another needed builtin.
> The above patch adds among other things __builtin_nextafterf16
> builtin which we need in order to constexpr evaluate
> std::nextafter(_Float16) overload (patch for that to be posted momentarily).
> While there is inline implementation of the overload, it isn't constant
> evaluation friendly, and the builtin doesn't need libm implementation
> because it will be used only during constant expression evaluation.
> We need the same thing also for std::nextafter(__gnu_cxx::__bfloat16_t)
> though and this patch does that.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> 2022-10-21 Jakub Jelinek <jakub@redhat.com>
>
> * builtin-types.def (BT_FN_BFLOAT16_BFLOAT16_BFLOAT16): New.
> * builtins.def (BUILT_IN_NEXTAFTERF16B): New builtin.
> * fold-const-call.cc (fold_const_call_sss): Handle
> CFN_BUILT_IN_NEXTAFTERF16B.
OK
jeff
prev parent reply other threads:[~2022-10-24 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 7:23 Jakub Jelinek
2022-10-21 15:42 ` [PATCH] builtins: Add various complex builtins for _Float{16,32,64,128,32x,64x,128x} Jakub Jelinek
2022-10-24 16:28 ` Jeff Law
2022-10-25 9:03 ` Patch ping Jakub Jelinek
2022-10-24 15:24 ` Jeff Law [this message]
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=28635ee5-0ff0-aeaa-0f8d-4c31d2e05159@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
--cc=rguenther@suse.de \
/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).