public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "g.peterhoff@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor Date: Thu, 29 Feb 2024 18:23:29 +0000 [thread overview] Message-ID: <bug-77776-4-8SWikRrxms@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776 g.peterhoff@t-online.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |g.peterhoff@t-online.de --- Comment #11 from g.peterhoff@t-online.de --- Would this be a good implementation for hypot3 in cmath? #define GCC_UNLIKELY(x) __builtin_expect(x, 0) #define GCC_LIKELY(x) __builtin_expect(x, 1) namespace __detail { template <typename _Tp> inline _GLIBCXX_CONSTEXPR typename enable_if<is_floating_point<_Tp>::value, bool>::type __isinf3(const _Tp __x, const _Tp __y, const _Tp __z) noexcept { return bool(int(std::isinf(__x)) | int(std::isinf(__y)) | int(std::isinf(__z))); } template <typename _Tp> inline _GLIBCXX_CONSTEXPR typename enable_if<is_floating_point<_Tp>::value, _Tp>::type __hypot3(_Tp __x, _Tp __y, _Tp __z) noexcept { __x = std::fabs(__x); __y = std::fabs(__y); __z = std::fabs(__z); const _Tp __max = std::fmax(std::fmax(__x, __y), __z); if (GCC_UNLIKELY(__max == _Tp{})) { return __max; } else { __x /= __max; __y /= __max; __z /= __max; return std::sqrt(__x*__x + __y*__y + __z*__z) * __max; } } } // __detail template <typename _Tp> inline _GLIBCXX_CONSTEXPR typename enable_if<is_floating_point<_Tp>::value, _Tp>::type __hypot3(const _Tp __x, const _Tp __y, const _Tp __z) noexcept { return (GCC_UNLIKELY(__detail::__isinf3(__x, __y, __z))) ? numeric_limits<_Tp>::infinity() : __detail::__hypot3(__x, __y, __z); } #undef GCC_UNLIKELY #undef GCC_LIKELY How does it work? * Basically, I first pull out the special case INFINITY (see https://en.cppreference.com/w/cpp/numeric/math/hypot). * As an additional safety measure (to prevent misuse) the functions are defined by enable_if. constexpr * The hypot3 functions can thus be defined as _GLIBCXX_CONSTEXPR. Questions * To get a better runtime behavior I define GCC_(UN)LIKELY. Are there already such macros (which I have overlooked)? * The functions are noexcept. Does that make sense? If yes: why are the math functions not noexcept? thx Gero
next prev parent reply other threads:[~2024-02-29 18:23 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-77776-4@http.gcc.gnu.org/bugzilla/> 2021-05-04 12:31 ` rguenth at gcc dot gnu.org 2024-02-29 18:23 ` g.peterhoff@t-online.de [this message] 2024-03-01 12:27 ` redi at gcc dot gnu.org 2024-03-02 15:52 ` g.peterhoff@t-online.de 2024-03-04 3:49 ` de34 at live dot cn 2024-03-04 10:45 ` mkretz at gcc dot gnu.org 2024-03-04 11:12 ` jakub at gcc dot gnu.org 2024-03-04 17:14 ` mkretz at gcc dot gnu.org 2024-03-04 20:21 ` jakub at gcc dot gnu.org 2024-03-06 2:47 ` g.peterhoff@t-online.de 2024-03-06 9:43 ` mkretz at gcc dot gnu.org 2024-03-06 12:35 ` redi at gcc dot gnu.org 2024-03-12 11:31 ` mkretz at gcc dot gnu.org 2024-03-19 0:09 ` g.peterhoff@t-online.de 2024-03-25 10:06 ` mkretz at gcc dot gnu.org 2024-04-05 1:08 ` g.peterhoff@t-online.de 2024-04-05 1:23 ` g.peterhoff@t-online.de 2024-04-10 16:41 ` g.peterhoff@t-online.de 2024-04-10 16:48 ` jakub at gcc dot gnu.org 2024-04-10 18:08 ` g.peterhoff@t-online.de
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-77776-4-8SWikRrxms@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: linkBe 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).