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++/59325] Provide a way to disable deprecated warnings Date: Sun, 21 Dec 2014 11:10:00 -0000 [thread overview] Message-ID: <bug-59325-4-tth2I3YOb5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59325-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59325 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- --- a/libstdc++-v3/include/bits/c++config +++ b/libstdc++-v3/include/bits/c++config @@ -78,11 +78,13 @@ # define _GLIBCXX_USE_DEPRECATED 1 #endif +#ifndef _GLIBCXX_DEPRECATED #if defined(__DEPRECATED) && (__cplusplus >= 201103L) # define _GLIBCXX_DEPRECATED __attribute__ ((__deprecated__)) #else # define _GLIBCXX_DEPRECATED #endif +#endif // Macros for ABI tag attributes. #ifndef _GLIBCXX_ABI_TAG_CXX11 This would allow you to just define _GLIBCXX_DEPRECATED="" unconditionally
next prev parent reply other threads:[~2014-12-21 11:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-28 8:40 [Bug libstdc++/59325] New: " andysem at mail dot ru 2013-11-28 11:14 ` [Bug libstdc++/59325] " redi at gcc dot gnu.org 2013-11-28 11:43 ` andysem at mail dot ru 2013-11-28 12:23 ` redi at gcc dot gnu.org 2013-11-28 13:03 ` andysem at mail dot ru 2014-12-21 11:10 ` redi at gcc dot gnu.org [this message] 2020-10-20 14:28 ` redi at gcc dot gnu.org 2020-10-20 14:32 ` redi at gcc dot gnu.org 2020-10-20 14:46 ` andysem at mail dot ru 2020-10-20 16:07 ` redi 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-59325-4-tth2I3YOb5@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).