public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4629] libsanitizer: Fix up libbacktrace build after r13-4547 [PR108072]
Date: Tue, 13 Dec 2022 09:33:56 +0000 (GMT)	[thread overview]
Message-ID: <20221213093356.E64F938715B6@sourceware.org> (raw)

https://gcc.gnu.org/g:0a43f7b1a73c8e3b9cefffe430274d0a3d6d3291

commit r13-4629-g0a43f7b1a73c8e3b9cefffe430274d0a3d6d3291
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Dec 13 10:30:36 2022 +0100

    libsanitizer: Fix up libbacktrace build after r13-4547 [PR108072]
    
    The r13-4547 commit added new non-static function to libbacktrace:
    backtrace_uncompress_zstd but for the libsanitizer use we need to
    rename it, so that it is in __asan_* namespace and doesn't clash
    with other copies of libbacktrace.
    
    2022-12-13  Jakub Jelinek  <jakub@redhat.com>
    
    libsanitizer/
            PR sanitizer/108072
            * libbacktrace/backtrace-rename.h (backtrace_uncompress_zstd): Define.

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

diff --git a/libsanitizer/libbacktrace/backtrace-rename.h b/libsanitizer/libbacktrace/backtrace-rename.h
index 2ec37a3307f..a31917c9af5 100644
--- a/libsanitizer/libbacktrace/backtrace-rename.h
+++ b/libsanitizer/libbacktrace/backtrace-rename.h
@@ -13,6 +13,7 @@
 #define backtrace_syminfo __asan_backtrace_syminfo
 #define backtrace_uncompress_lzma __asan_backtrace_uncompress_lzma
 #define backtrace_uncompress_zdebug __asan_backtrace_uncompress_zdebug
+#define backtrace_uncompress_zstd __asan_backtrace_uncompress_zstd
 #define backtrace_vector_finish __asan_backtrace_vector_finish
 #define backtrace_vector_grow __asan_backtrace_vector_grow
 #define backtrace_vector_release __asan_backtrace_vector_release

                 reply	other threads:[~2022-12-13  9:33 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=20221213093356.E64F938715B6@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-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).