From: "Steinar H. Gunderson" <sesse@google.com>
To: acme@kernel.org
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
irogers@google.com
Subject: Re: [PATCH v7 4/4] perf report: LLVM-based symbol listing
Date: Sun, 2 Jun 2024 22:39:46 +0200 [thread overview]
Message-ID: <ZlzYkpybqom9hvJx@google.com> (raw)
In-Reply-To: <20240526182212.544525-4-sesse@google.com>
On Sun, May 26, 2024 at 08:22:12PM +0200, Steinar H. Gunderson wrote:
> Similar to the previous LLVM patches, this allows symbol enumeration
> using LLVM instead of libbfd or libelf. This allows distro builds to
> reliably enumerate symbols in e.g. PE binaries as profiled with WINE.
>
> A lot of the logic for e.g. length detection has been carried over
> from the libbfd code.
I'm dropping this patch; I don't need it myself, it hits some bugs, and
I don't have the resources to see it through. I'll send v8 of the rest
of the series soon.
/* Steinar */
next prev parent reply other threads:[~2024-06-02 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 18:22 [PATCH v7 1/4] perf report: Support LLVM for addr2line() Steinar H. Gunderson
2024-05-26 18:22 ` [PATCH v7 2/4] perf annotate: split out read_symbol() Steinar H. Gunderson
2024-05-26 18:22 ` [PATCH v7 3/4] perf annotate: LLVM-based disassembler Steinar H. Gunderson
2024-05-29 4:06 ` Namhyung Kim
2024-06-02 20:38 ` Steinar H. Gunderson
2024-05-26 18:22 ` [PATCH v7 4/4] perf report: LLVM-based symbol listing Steinar H. Gunderson
2024-05-26 21:24 ` Steinar H. Gunderson
2024-05-29 4:11 ` Namhyung Kim
2024-06-02 20:39 ` Steinar H. Gunderson [this message]
2024-05-29 3:56 ` [PATCH v7 1/4] perf report: Support LLVM for addr2line() Namhyung Kim
2024-05-29 13:52 ` Arnaldo Carvalho de Melo
2024-05-30 16:55 ` Namhyung Kim
2024-05-30 16:58 ` Namhyung Kim
2024-06-02 20:37 ` Steinar H. Gunderson
2024-06-05 1:13 ` Namhyung Kim
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=ZlzYkpybqom9hvJx@google.com \
--to=sesse@google.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.