From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Steinar H. Gunderson" <sesse@google.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
irogers@google.com, Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v9 1/3] perf report: Support LLVM for addr2line()
Date: Mon, 9 Sep 2024 13:42:26 -0300 [thread overview]
Message-ID: <Zt8lclBTUpZcxQqP@x1> (raw)
In-Reply-To: <Zt3yemuoUCXTaClB@google.com>
On Sun, Sep 08, 2024 at 08:52:42PM +0200, Steinar H. Gunderson wrote:
> On Tue, Sep 03, 2024 at 11:15:39AM -0300, Arnaldo Carvalho de Melo wrote:
> > Or, as I'll do with debian:11, just remove llvm-dev and not build the
> > features it enables:
>
> Thanks for looking into this! Is there anything I should be doing,
> or are the patches you posted earlier sufficient?
Everything was merged already, I was just mentioning that we don't
support building with llvm-dev in debian:11 and a few other distros
where the version is old and doesn't match what is being used in perf.
- Arnaldo
next prev parent reply other threads:[~2024-09-09 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 15:00 [PATCH v9 1/3] perf report: Support LLVM for addr2line() Steinar H. Gunderson
2024-07-19 15:00 ` [PATCH v9 2/3] perf annotate: split out read_symbol() Steinar H. Gunderson
2024-07-19 15:00 ` [PATCH v9 3/3] perf annotate: LLVM-based disassembler Steinar H. Gunderson
2024-09-02 14:53 ` Arnaldo Carvalho de Melo
2024-09-02 14:55 ` Arnaldo Carvalho de Melo
2024-07-30 19:42 ` [PATCH v9 1/3] perf report: Support LLVM for addr2line() Arnaldo Carvalho de Melo
2024-07-30 19:49 ` Arnaldo Carvalho de Melo
2024-08-03 15:11 ` Steinar H. Gunderson
2024-09-01 10:57 ` Steinar H. Gunderson
2024-09-03 10:09 ` Arnaldo Carvalho de Melo
2024-09-03 13:14 ` Arnaldo Carvalho de Melo
2024-09-03 14:01 ` Arnaldo Carvalho de Melo
2024-09-03 14:15 ` Arnaldo Carvalho de Melo
2024-09-08 18:52 ` Steinar H. Gunderson
2024-09-09 16:42 ` Arnaldo Carvalho de Melo [this message]
2024-09-10 14:06 ` James Clark
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=Zt8lclBTUpZcxQqP@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sesse@google.com \
/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 NNTP newsgroup(s).