public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109818] std::trunc() requires a <cmath> hack after building DJGPP Date: Wed, 31 May 2023 20:20:16 +0000 [thread overview] Message-ID: <bug-109818-4-h4gyLggShO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109818-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109818 --- Comment #30 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:49f59826c66bcaa3531429381b4aed944c332e5b commit r14-1454-g49f59826c66bcaa3531429381b4aed944c332e5b Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed May 31 12:22:06 2023 +0100 libstdc++: Add separate autoconf macro for std::float_t and std::double_t [PR109818] This should make it possible to use openlibm with djgpp (and other targets with missing C99 <math.h> functions). The <math.h> from openlibm provides all the functions, but not the float_t and double_t typedefs. By separating the autoconf checks for the functionsand the typedefs, we don't disable support for all the functions just because those typedefs are not present. libstdc++-v3/ChangeLog: PR libstdc++/109818 * acinclude.m4 (GLIBCXX_ENABLE_C99): Add separate check for float_t and double_t and define HAVE_C99_FLT_EVAL_TYPES. * config.h.in: Regenerate. * configure: Regenerate. * include/c_global/cmath (float_t, double_t): Guard using new _GLIBCXX_HAVE_C99_FLT_EVAL_TYPES macro.
next prev parent reply other threads:[~2023-05-31 20:20 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 18:42 [Bug libstdc++/109818] New: " janezz55 at gmail dot com 2023-05-11 20:11 ` [Bug libstdc++/109818] " redi at gcc dot gnu.org 2023-05-11 20:13 ` redi at gcc dot gnu.org 2023-05-11 20:56 ` janezz55 at gmail dot com 2023-05-11 21:13 ` redi at gcc dot gnu.org 2023-05-11 21:14 ` redi at gcc dot gnu.org 2023-05-11 21:27 ` janezz55 at gmail dot com 2023-05-11 22:17 ` redi at gcc dot gnu.org 2023-05-12 5:21 ` janezz55 at gmail dot com 2023-05-12 6:05 ` janezz55 at gmail dot com 2023-05-12 8:07 ` redi at gcc dot gnu.org 2023-05-12 8:15 ` redi at gcc dot gnu.org 2023-05-12 10:14 ` janezz55 at gmail dot com 2023-05-12 10:16 ` redi at gcc dot gnu.org 2023-05-12 10:23 ` janezz55 at gmail dot com 2023-05-12 10:48 ` redi at gcc dot gnu.org 2023-05-12 10:55 ` redi at gcc dot gnu.org 2023-05-12 16:35 ` janezz55 at gmail dot com 2023-05-12 16:45 ` redi at gcc dot gnu.org 2023-05-12 21:21 ` redi at gcc dot gnu.org 2023-05-12 21:58 ` redi at gcc dot gnu.org 2023-05-12 22:01 ` redi at gcc dot gnu.org 2023-05-12 23:17 ` janezz55 at gmail dot com 2023-05-12 23:43 ` redi at gcc dot gnu.org 2023-05-13 1:19 ` janezz55 at gmail dot com 2023-05-13 9:55 ` redi at gcc dot gnu.org 2023-05-13 13:01 ` janezz55 at gmail dot com 2023-05-14 12:26 ` janezz55 at gmail dot com 2023-05-14 19:56 ` redi at gcc dot gnu.org 2023-05-14 20:02 ` redi at gcc dot gnu.org 2023-05-31 20:20 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-31 20:24 ` redi at gcc dot gnu.org 2023-05-31 23:03 ` janezz55 at gmail dot com 2023-06-01 10:41 ` 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-109818-4-h4gyLggShO@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).