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 libstdc++/114018] std::nexttoward is not implemented for C++23-FP-Types
Date: Tue, 20 Feb 2024 22:57:52 +0000	[thread overview]
Message-ID: <bug-114018-4-uqg89K8gXV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114018-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
> So, do we need to define those and std::unreachable (); in their bodies or
> something similar?

Though, cmath probably can't #include <utility>, so
#ifdef _GLIBCXX_DEBUG
    std::__glibcxx_assert_fail(nullptr, 0, "std::nexttoward with extended
floating point type", nullptr);
#elif defined _GLIBCXX_ASSERTIONS
    __builtin_trap();
#else
    __builtin_unreachable();
#endif
or something similar.
Jon, I can try to write it tomorrow if you tell me what you prefer.

  parent reply	other threads:[~2024-02-20 22:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 19:35 [Bug libstdc++/114018] New: " g.peterhoff@t-online.de
2024-02-20 20:06 ` [Bug libstdc++/114018] " pinskia at gcc dot gnu.org
2024-02-20 20:07 ` pinskia at gcc dot gnu.org
2024-02-20 20:18 ` redi at gcc dot gnu.org
2024-02-20 22:27 ` jsm28 at gcc dot gnu.org
2024-02-20 22:28 ` jakub at gcc dot gnu.org
2024-02-20 22:33 ` pinskia at gcc dot gnu.org
2024-02-20 22:37 ` jakub at gcc dot gnu.org
2024-02-20 22:40 ` jakub at gcc dot gnu.org
2024-02-20 22:57 ` jakub at gcc dot gnu.org [this message]
2024-02-21  0:24 ` redi at gcc dot gnu.org
2024-02-21  7:24 ` jakub at gcc dot gnu.org
2024-02-21  8:23 ` de34 at live dot cn
2024-02-21  8:44 ` jakub at gcc dot gnu.org
2024-02-21  8:54 ` jakub at gcc dot gnu.org
2024-02-21 11:55 ` redi at gcc dot gnu.org
2024-02-21 12:00 ` redi at gcc dot gnu.org
2024-02-21 12:02 ` redi at gcc dot gnu.org
2024-02-21 12:06 ` jakub at gcc dot gnu.org
2024-02-21 12:12 ` redi at gcc dot gnu.org
2024-05-21  9:19 ` jakub at gcc dot gnu.org

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-114018-4-uqg89K8gXV@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).