From: "Steinar H. Gunderson" <sesse@google.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: acme@kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, irogers@google.com
Subject: Re: [PATCH v4 1/3] perf report: Support LLVM for addr2line()
Date: Thu, 23 May 2024 11:32:11 +0200 [thread overview]
Message-ID: <Zk8NG10oHcQ0T6EQ@google.com> (raw)
In-Reply-To: <CAM9d7cjjH63CC8r-z33P4SCWw3x4NMxuSC1CovVHqpp-zXSf6g@mail.gmail.com>
On Wed, May 22, 2024 at 01:46:35PM -0700, Namhyung Kim wrote:
> Great! Personally I found libbfd is hard to read (and use). Hope
> that libllvm is better in that pov. I'm not sure if we all want to
> remove the libbfd dependency but at least we can select one of
> them at build time. Maybe the same for libelf and libdw(fl) too.
I've never used either before, but I found libllvm pretty
straightforward. The C/C++ interop is a bit painful, though.
(The disassembler has a C interface, but addr2line does not,
from what I could see.)
> Having symbol enumeration and demangling with LLVM would
> be nice but not required to merge this work. I'll take a deeper
> look next week. Please post v5.
Posted.
/* Steinar */
next prev parent reply other threads:[~2024-05-23 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 8:30 [PATCH v4 1/3] perf report: Support LLVM for addr2line() Steinar H. Gunderson
2024-05-20 8:30 ` [PATCH v4 2/3] perf annotate: split out read_symbol() Steinar H. Gunderson
2024-05-20 8:30 ` [PATCH v4 3/3] perf annotate: LLVM-based disassembler Steinar H. Gunderson
2024-05-22 17:27 ` [PATCH v4 1/3] perf report: Support LLVM for addr2line() Namhyung Kim
2024-05-22 19:50 ` Steinar H. Gunderson
2024-05-22 20:46 ` Namhyung Kim
2024-05-23 9:32 ` Steinar H. Gunderson [this message]
2024-05-23 13:38 ` Arnaldo Carvalho de Melo
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=Zk8NG10oHcQ0T6EQ@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 \
--cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox