public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kip at thevertigo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/79700] std::fabsf and std::fabsl missing from <cmath>
Date: Thu, 24 Dec 2020 01:02:11 +0000	[thread overview]
Message-ID: <bug-79700-4-DZUcj8I9Yk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79700-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Kip Warner <kip at thevertigo dot com> ---
Thanks Jonathan, but I still think you are mistaken in that you don't
understand why the function exists in its various forms. Your explanation is
technical and not philosophical.

Whether it was originally inherited from the standard C library or was a
creature of a C++ WG committee isn't material. And yes, you are being
speculative. 

We can discuss another day the history, design choices, and rationale behind
how floating point calculations have been done. In any event, we are going
around in circles.

But the important thing is that this is thankfully being patched.

  parent reply	other threads:[~2020-12-24  1:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-79700-4@http.gcc.gnu.org/bugzilla/>
2020-12-22 23:31 ` kip at thevertigo dot com
2020-12-23  8:34 ` redi at gcc dot gnu.org
2020-12-23 17:33 ` kip at thevertigo dot com
2020-12-23 20:48 ` redi at gcc dot gnu.org
2020-12-23 20:52 ` redi at gcc dot gnu.org
2020-12-23 22:06 ` kip at thevertigo dot com
2020-12-23 23:04 ` redi at gcc dot gnu.org
2020-12-23 23:09 ` kip at thevertigo dot com
2020-12-24  0:42 ` redi at gcc dot gnu.org
2020-12-24  1:02 ` kip at thevertigo dot com [this message]
2021-03-02 10:57 ` redi at gcc dot gnu.org
2021-03-24 14:26 ` redi at gcc dot gnu.org
2021-08-11  3:27 ` hewillk at gmail dot com
2022-04-19  9:10 ` de34 at live dot cn
2022-04-22  3:37 ` de34 at live dot cn
2022-05-06  8:29 ` jakub at gcc dot gnu.org
2022-05-06  8:47 ` redi at gcc dot gnu.org
2023-04-26  6:55 ` rguenth at gcc dot gnu.org
2023-07-27  9:22 ` rguenth at gcc dot gnu.org
2023-07-27 10:42 ` redi at gcc dot gnu.org
2023-11-11  0:41 ` cvs-commit at gcc dot gnu.org
2023-11-11  1:04 ` 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-79700-4-DZUcj8I9Yk@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).