public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/109758] std::abs(__float128) doesn't support NaN
Date: Mon, 08 May 2023 08:29:45 +0000	[thread overview]
Message-ID: <bug-109758-4-NUWN9gB43b@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109758-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to g.peterhoff from comment #7)
> 1) Can you please still submit a proposal to the STD/ISO committee so that
> abs (besides copysign/signbit) ALWAYS works ?

What does that even mean?

Should abs("") work?

Why should the committee say anything about the behaviour of a non-standard
__float128 type?

So no, I won't submit anything related to this to the committee. This is just a
bug in a libstdc++ function, like I already said.


> 2) What do you think about my proposal for a C++ interface quadmath.hpp ?

I already said we don't want to do that. If you want full support in the
standard library, use standard types.

  parent reply	other threads:[~2023-05-08  8:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 17:44 [Bug libquadmath/109758] New: quadmath abs g.peterhoff@t-online.de
2023-05-06 20:33 ` [Bug libstdc++/109758] " jakub at gcc dot gnu.org
2023-05-06 22:15 ` [Bug libstdc++/109758] std::abs(__float128) doesn't support NaN redi at gcc dot gnu.org
2023-05-06 22:48 ` g.peterhoff@t-online.de
2023-05-06 22:57 ` redi at gcc dot gnu.org
2023-05-06 23:06 ` g.peterhoff@t-online.de
2023-05-06 23:09 ` redi at gcc dot gnu.org
2023-05-07  0:09 ` g.peterhoff@t-online.de
2023-05-07 10:04 ` jakub at gcc dot gnu.org
2023-05-08  8:29 ` redi at gcc dot gnu.org [this message]
2023-05-08  8:31 ` redi at gcc dot gnu.org
2023-05-08  8:47 ` jakub at gcc dot gnu.org
2023-05-08 16:40 ` redi at gcc dot gnu.org
2023-05-11 11:55 ` cvs-commit at gcc dot gnu.org
2023-05-11 11:57 ` redi at gcc dot gnu.org
2023-05-11 12:12 ` redi at gcc dot gnu.org
2023-06-01 22:44 ` cvs-commit at gcc dot gnu.org
2023-06-01 22:45 ` redi at gcc dot gnu.org
2024-03-18 14:05 ` cvs-commit at gcc dot gnu.org
2024-03-18 14:12 ` redi 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-109758-4-NUWN9gB43b@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).