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 c/114181] issubnormal is a macro Date: Fri, 01 Mar 2024 11:05:51 +0000 [thread overview] Message-ID: <bug-114181-4-ZY2n1Fyppr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114181-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114181 --- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> --- Libc headers define lots of macros, we don't #undef them in C++ headers unless they use the name of a function defined by the C++ library (because C++ says its library functions must be real functions and must not be hidden by macros). If you want to provide an implementation of issubnormal (e.g. as boost::issubnormal) then you need to do: #include <math.h> #undef issubnormal I don't think it's a libstdc++ bug that we don't #undef non-standard macros. It's certainly not a GCC component=c bug that Glibc defines a macro in its <math.h>. So there's no GCC bug here. Like Andrew said, iff we need to define std::issubnormal then we'll #undef it, but we're not going to do that until we need to.
next prev parent reply other threads:[~2024-03-01 11:05 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-01 0:27 [Bug c/114181] New: " g.peterhoff@t-online.de 2024-03-01 0:32 ` [Bug c/114181] " pinskia at gcc dot gnu.org 2024-03-01 0:35 ` pinskia at gcc dot gnu.org 2024-03-01 0:41 ` g.peterhoff@t-online.de 2024-03-01 0:51 ` pinskia at gcc dot gnu.org 2024-03-01 1:04 ` g.peterhoff@t-online.de 2024-03-01 1:07 ` pinskia at gcc dot gnu.org 2024-03-01 1:08 ` pinskia at gcc dot gnu.org 2024-03-01 1:14 ` g.peterhoff@t-online.de 2024-03-01 1:17 ` pinskia at gcc dot gnu.org 2024-03-01 2:20 ` g.peterhoff@t-online.de 2024-03-01 2:38 ` pinskia at gcc dot gnu.org 2024-03-01 3:08 ` g.peterhoff@t-online.de 2024-03-01 3:19 ` pinskia at gcc dot gnu.org 2024-03-01 11:05 ` redi at gcc dot gnu.org [this message] 2024-03-01 11:19 ` jakub 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-114181-4-ZY2n1Fyppr@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).