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++/97044] Undefined format macros because of include order on AIX Date: Sun, 20 Sep 2020 22:18:32 +0000 [thread overview] Message-ID: <bug-97044-4-b50fRnJYbw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97044-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97044 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Specifically, C99 7.8.1 footnote 182 says: "C++ implementations should define these macros only when _ _STDC_FORMAT_MACROS is defined before <inttypes.h> is included." The footnote is not present in C11. C++11 27.9.2 p3 says: "Note: The macros defined by <cinttypes> are provided unconditionally. In particular, the symbol __STDC_FORMAT_MACROS, mentioned in footnote 182 of the C standard, plays no role in C++." So requiring the macro to be defined by C++ programs before including <inttypes.h> is an anachronism that is not compatible with any version of the C++ standard.
next prev parent reply other threads:[~2020-09-20 22:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-14 9:07 [Bug libstdc++/97044] New: " clement.chigot at atos dot net 2020-09-20 20:10 ` [Bug libstdc++/97044] " redi at gcc dot gnu.org 2020-09-20 22:18 ` redi at gcc dot gnu.org [this message] 2020-09-21 8:13 ` clement.chigot at atos dot net 2020-09-21 12:48 ` dje at gcc dot gnu.org 2020-09-26 16:01 ` [Bug target/97044] " cvs-commit 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-97044-4-b50fRnJYbw@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).