public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/65281] Lots of macros using non-reserved names in gthr headers Date: Mon, 08 Apr 2024 22:40:39 +0000 [thread overview] Message-ID: <bug-65281-4-I6Zl59LSxj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65281-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65281 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Actually HIDE_EXPORTS has been handled as _GLIBCXX_HIDE_EXPORTS for a long time now. And UNUSED has also been handled as _GLIBCXX_UNUSED too for a long time (since 2001). This is all handled by the code in libstdc++/include/Makefile.in which does the renaming there. I don't see any references in libstdc++ usage where it places a macro in non-implementation space.
prev parent reply other threads:[~2024-04-08 22:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-02 18:11 [Bug libgcc/65281] New: " redi at gcc dot gnu.org 2015-03-02 18:15 ` [Bug libgcc/65281] " redi at gcc dot gnu.org 2024-04-08 22:40 ` pinskia at gcc dot gnu.org [this message]
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-65281-4-I6Zl59LSxj@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).