public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107543] New: c-family/c-cppbuiltin.cc: Undefine __GNUC_STDC_INLINE__ in C++ mode? Date: Sun, 06 Nov 2022 21:39:44 +0000 [thread overview] Message-ID: <bug-107543-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107543 Bug ID: 107543 Summary: c-family/c-cppbuiltin.cc: Undefine __GNUC_STDC_INLINE__ in C++ mode? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: i at maskray dot me Target Milestone: --- -fgnu89-inline / C99 / C++ inline modes are all different. For C++, perhaps neither __GNUC_STDC_INLINE__ nor __GNUC_GNUC_INLINE__ should be defined. % g++ -dM -E -xc++ /dev/null | grep __GNUC_STDC_INLINE__ #define __GNUC_STDC_INLINE__ 1 gcc/doc/cpp.texi does not talk about C++ @item __GNUC_STDC_INLINE__ GCC defines this macro if functions declared @code{inline} will be handled according to the ISO C99 or later standards. Object files will contain externally visible definitions of all functions declared @code{extern inline}. They will not contain definitions of any functions declared @code{inline} without @code{extern}. If this macro is defined, GCC supports the @code{gnu_inline} function attribute as a way to always get the gnu90 behavior. Side note: there is "warning: command-line option ‘-fgnu89-inline’ is valid for C/ObjC but not for C++" but __attribute__((gnu_inline)) is usable in C++ mode and has strange codegen behaviors.
reply other threads:[~2022-11-06 21:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-107543-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).