public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r13-6323] libstdc++: Suppress warnings about use of deprecated std::aligned_storage Date: Fri, 24 Feb 2023 14:25:07 +0000 (GMT) [thread overview] Message-ID: <20230224142507.B510D3858284@sourceware.org> (raw) https://gcc.gnu.org/g:ae390479340ff49873c22cd7a301acbf67eca30b commit r13-6323-gae390479340ff49873c22cd7a301acbf67eca30b Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Feb 23 17:37:59 2023 +0000 libstdc++: Suppress warnings about use of deprecated std::aligned_storage libstdc++-v3/ChangeLog: * include/ext/aligned_buffer.h (__aligned_buffer): Add diagnostic pragmas. Diff: --- libstdc++-v3/include/ext/aligned_buffer.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libstdc++-v3/include/ext/aligned_buffer.h b/libstdc++-v3/include/ext/aligned_buffer.h index 765d14684f2..dc62dfc8741 100644 --- a/libstdc++-v3/include/ext/aligned_buffer.h +++ b/libstdc++-v3/include/ext/aligned_buffer.h @@ -81,6 +81,8 @@ namespace __gnu_cxx template<typename _Tp> using __aligned_buffer = __aligned_membuf<_Tp>; #else +#pragma GCC diagnostic push +#pragma GCC diagnostic ignored "-Wdeprecated-declarations" // Similar to __aligned_membuf but aligned for complete objects, not members. // This type is used in <forward_list>, <future>, <bits/shared_ptr_base.h> // and <bits/hashtable_policy.h>, but ideally they would use __aligned_membuf @@ -118,6 +120,7 @@ namespace __gnu_cxx _M_ptr() const noexcept { return static_cast<const _Tp*>(_M_addr()); } }; +#pragma GCC diagnostic pop #endif } // namespace
reply other threads:[~2023-02-24 14:25 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=20230224142507.B510D3858284@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).