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-153] libstdc++: Do not include <cxxabi.h> in <stacktrace> Date: Fri, 6 May 2022 13:45:16 +0000 (GMT) [thread overview] Message-ID: <20220506134516.330A33856DFA@sourceware.org> (raw) https://gcc.gnu.org/g:e112e37f2920bcc9185e53b754d9145aac912c72 commit r13-153-ge112e37f2920bcc9185e53b754d9145aac912c72 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri May 6 13:23:45 2022 +0100 libstdc++: Do not include <cxxabi.h> in <stacktrace> This avoids polluting the global namespace with the "abi" namespace alias. libstdc++-v3/ChangeLog: * include/std/stacktrace: Do not include <cxxabi.h>. (__cxa_demangle): Declare. Diff: --- libstdc++-v3/include/std/stacktrace | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/include/std/stacktrace b/libstdc++-v3/include/std/stacktrace index 98ce9231150..8e6c79a2f4f 100644 --- a/libstdc++-v3/include/std/stacktrace +++ b/libstdc++-v3/include/std/stacktrace @@ -38,7 +38,6 @@ #include <bits/stl_iterator.h> #include <bits/stl_uninitialized.h> #include <ext/numeric_traits.h> -#include <cxxabi.h> struct __glibcxx_backtrace_state; struct __glibcxx_backtrace_simple_data; @@ -70,6 +69,13 @@ __glibcxx_backtrace_syminfo(__glibcxx_backtrace_state*, uintptr_t addr, void*); } +namespace __cxxabiv1 +{ + extern "C" char* + __cxa_demangle(const char* __mangled_name, char* __output_buffer, + size_t* __length, int* __status); +} + namespace std _GLIBCXX_VISIBILITY(default) { _GLIBCXX_BEGIN_NAMESPACE_VERSION
reply other threads:[~2022-05-06 13:45 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=20220506134516.330A33856DFA@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).