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++/109818] std::trunc() requires a <cmath> hack after building DJGPP
Date: Fri, 12 May 2023 10:55:42 +0000 [thread overview]
Message-ID: <bug-109818-4-ilLtac78o6@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
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #16 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Most of the missing functions are the long double variants. We could certainly
have a separate macro for long double math, which might help several targets.
The other missing ones are fdim, fma, fmin, fmax, nearbyint, nexttoward,
remoquo, scalbln and tgamma, which are missing for all of float, double and
long double. We could have a separate check for those.
next prev parent reply other threads:[~2023-05-12 10:55 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 [this message]
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
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-ilLtac78o6@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).