public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/114101] FAIL: 26_numerics/headers/cmath/functions_std_c++17.cc -std=gnu++17 (test for excess errors)
Date: Sun, 25 Feb 2024 19:52:53 +0000 [thread overview]
Message-ID: <bug-114101-4-JTmk28tz7H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114101-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
--- Comment #2 from dave.anglin at bell dot net ---
On 2024-02-25 2:17 p.m., redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114101
>
> Jonathan Wakely <redi at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> See Also| |https://gcc.gnu.org/bugzill
> | |a/show_bug.cgi?id=79700
The patch I posted allows HP-UX targets to make use of the above change. I
defined
_GLIBCXX_USE_C99_MATH_FUNCS and _GLIBCXX_USE_BUILTIN_FMAF in
config/os/hpux/os_defines.h:
+// Import C99 functions in <math.h> in <cmath> in namespace std in C++11.
+// Missing functions are handled by stubs. The fma, nexttoward, scalbln
+// and tgamma are missing in HP-UX 11. Many float variants are supported.
+#define _GLIBCXX_USE_C99_MATH_FUNCS 1
+#define _GLIBCXX_USE_C99_MATH_TR1 1
Had to add double stubs for fma, nexttoward, scalbln and tgamma to complete the
set
of required functions.
Currently, _GLIBCXX_USE_C99_MATH_FUNCS and _GLIBCXX_USE_C99_MATH_TR1 are
only enabled when configure detects the full set of C99 functions.
next prev parent reply other threads:[~2024-02-25 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 16:56 [Bug libstdc++/114101] New: " danglin at gcc dot gnu.org
2024-02-25 17:17 ` [Bug libstdc++/114101] " danglin at gcc dot gnu.org
2024-02-25 19:52 ` dave.anglin at bell dot net [this message]
2024-02-25 20:09 ` dave.anglin at bell dot net
2024-02-25 20:33 ` dave.anglin at bell dot net
2024-02-25 20:45 ` danglin at gcc dot gnu.org
2024-02-25 21:04 ` dave.anglin at bell dot net
2024-02-25 21:51 ` dave.anglin at bell dot net
2024-03-01 23:15 ` danglin at gcc dot gnu.org
2024-03-22 14:38 ` danglin at gcc dot gnu.org
2024-03-22 19:00 ` redi at gcc dot gnu.org
2024-03-22 20:15 ` dave.anglin at bell dot net
2024-03-23 0:33 ` redi at gcc dot gnu.org
2024-03-23 18:09 ` dave.anglin at bell dot net
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-114101-4-JTmk28tz7H@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).