public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-4682] libstdc++: Update backtrace-rename.h
Date: Tue, 13 Dec 2022 21:16:12 +0000 (GMT)	[thread overview]
Message-ID: <20221213211612.9263F3838CC9@sourceware.org> (raw)

https://gcc.gnu.org/g:f82afb6976411b0eca0c50f49cf889cce4df8919

commit r13-4682-gf82afb6976411b0eca0c50f49cf889cce4df8919
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Dec 13 22:15:29 2022 +0100

    libstdc++: Update backtrace-rename.h
    
    When writing the r13-4629 commit log I've realized that libsanitizer
    isn't the only place which nowadays renames libbacktrace symbols,
    libstdc++ does that too.
    
    2022-12-13  Jakub Jelinek  <jakub@redhat.com>
    
            * src/libbacktrace/backtrace-rename.h (backtrace_uncompress_zstd):
            Define.

Diff:
---
 libstdc++-v3/src/libbacktrace/backtrace-rename.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/libstdc++-v3/src/libbacktrace/backtrace-rename.h b/libstdc++-v3/src/libbacktrace/backtrace-rename.h
index 79bdef6309f..5417532480e 100644
--- a/libstdc++-v3/src/libbacktrace/backtrace-rename.h
+++ b/libstdc++-v3/src/libbacktrace/backtrace-rename.h
@@ -16,6 +16,7 @@
 #define backtrace_syminfo __glibcxx_backtrace_syminfo
 #define backtrace_uncompress_lzma __glibcxx_backtrace_uncompress_lzma
 #define backtrace_uncompress_zdebug __glibcxx_backtrace_uncompress_zdebug
+#define backtrace_uncompress_zstd __glibcxx_backtrace_uncompress_zstd
 #define backtrace_vector_finish __glibcxx_backtrace_vector_finish
 #define backtrace_vector_grow __glibcxx_backtrace_vector_grow
 #define backtrace_vector_release __glibcxx_backtrace_vector_release

                 reply	other threads:[~2022-12-13 21:16 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=20221213211612.9263F3838CC9@sourceware.org \
    --to=jakub@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: link
Be 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).