From: Namhyung Kim <namhyung@kernel.org>
To: "Steinar H. Gunderson" <sesse@google.com>
Cc: acme@kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, irogers@google.com,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH v7 1/4] perf report: Support LLVM for addr2line()
Date: Tue, 4 Jun 2024 18:13:34 -0700 [thread overview]
Message-ID: <Zl-7vorESdIgbwIG@google.com> (raw)
In-Reply-To: <ZlzYEp78ihsGeEEi@google.com>
On Sun, Jun 02, 2024 at 10:37:38PM +0200, Steinar H. Gunderson wrote:
> On Thu, May 30, 2024 at 09:58:09AM -0700, Namhyung Kim wrote:
> > Can you please add something to tests/mask so that
> > we can test the build with and without libllvm easily?
>
> I have no idea what this is (it doesn't seem to be a file or directory).
> Do you have a pointer where I can get more information?
Sorry, it was tools/perf/tests/make (not mask). We keep combinations
of build configurations and test it with `make build-test`.
Thanks,
Namhyung
prev parent reply other threads:[~2024-06-05 1:13 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
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 [this message]
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=Zl-7vorESdIgbwIG@google.com \
--to=namhyung@kernel.org \
--cc=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=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 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.