public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109924] missing __builtin_nanf16b
Date: Sat, 03 Jun 2023 15:13:21 +0000	[thread overview]
Message-ID: <bug-109924-4-VUU32EcdIf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109924-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109924

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I certainly don't see that stated there anywhere.
Furthermore, _Float16 and __bf16 are nothing but normal FP types, there is to
this date no C library support for those formats, and at least for the latter
the only hw support which appears are better or worse instructions to convert
those to float and back.
So, bfloat16_t support is really done using float math library functions and
builtins,
and as I said the only builtins which were added were the really required one
to be able to constexpr evaluate what C++23 mandates.

      parent reply	other threads:[~2023-06-03 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-21 10:29 [Bug c++/109924] New: " g.peterhoff@t-online.de
2023-05-21 15:00 ` [Bug c++/109924] " jakub at gcc dot gnu.org
2023-05-22  8:59 ` redi at gcc dot gnu.org
2023-06-03 14:23 ` g.peterhoff@t-online.de
2023-06-03 15:13 ` jakub at gcc dot gnu.org [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=bug-109924-4-VUU32EcdIf@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).