public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clement.chigot at atos dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/97044] New: Undefined format macros because of include order on AIX Date: Mon, 14 Sep 2020 09:07:03 +0000 [thread overview] Message-ID: <bug-97044-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97044 Bug ID: 97044 Summary: Undefined format macros because of include order on AIX Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: clement.chigot at atos dot net Target Milestone: --- On AIX, C++ format macros like "PRIu32" might not be defined even if "cinttypes" is included. It happends when other headers which have a dependency on "inttypes.h" are included before. On AIX, __STDC_FORMAT_MACROS must be defined before "sys/inttypes.h" is included in order to have these macros defined. But with for example <cstring>, as "string.h" includes "sys/types" which included "sys/inttypes.h", __STDC_FORMAT_MACROS won't be defined when "sys/inttypes.h" is first included thus the format macros won't be defined. This program works on Linux but not on AIX. #include <cstring> #include <cinttypes> #include <iostream> int main(){ #ifdef PRIu32 std::cout << "PRIu32 defined" << std::endl; #else std::cout << "PRIu32 not defined" << std::endl; #endif } My question is what are the G++ standards saying on that ? Should <cinttypes> always defined "PRIu32"-like macros ? Or does the developers should be careful the order when are included the headers or always add -D__STDC_FORMAT_MACROS ? I would clearly go for one. Especially, because knowing that "#include <cstring>" must be after "#include <cinttypes>" if you want to use "PRIu32" is not obvious. Clément
next reply other threads:[~2020-09-14 9:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-14 9:07 clement.chigot at atos dot net [this message] 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 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@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).