From: sashiko-bot@kernel.org
To: "James Clark" <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables
Date: Fri, 06 Nov 2026 05:44:16 +0000 [thread overview]
Message-ID: <sashiko-outbox-200850@kernel.org> (raw)
In-Reply-To: <20261105-james-perf-test-fixes-v1-2-0b279bee5830@linaro.org>
> die_find_variable_by_addr() and die_collect_global_vars() only accept
> global variables with a DW_OP_addr location. DWARF 5 producers like
> clang use DW_OP_addrx instead, which is an index into .debug_addr, so
> global variables are never found when Perf is built with LLVM=1.
>
> Add a helper that also resolves DW_OP_addrx and DW_OP_GNU_addr_index
> through dwarf_getlocation_attr() and dwarf_formaddr(), and use it in
> both places. This fixes the "perf data type profiling tests" test:
>
> $ perf test -vvv "perf data type profiling tests"
> ...
> Basic C perf annotate test
> Basic annotate [Failed: missing target data type]
> ...
> Pipe C perf annotate test
> Pipe annotate [Failed: missing target data type]
> ...
> Basic FS perf annotate test
> Basic annotate [Failed: missing target data type]
> ...
> Pipe FS perf annotate test
> Pipe annotate [Failed: missing target data type]
> ---- end(-1) ----
> 88: perf data type profiling tests : FAILED!
>
> Fixes: d60469d7c0e5 ("perf dwarf-aux: Add die_find_variable_by_addr()")
> Signed-off-by: James Clark <james.clark@linaro.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105-james-perf-test-fixes-v1-0-0b279bee5830@linaro.org?part=2
next prev parent reply other threads:[~2026-11-06 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 15:49 [PATCH 0/4] perf tools: LLVM dwarf and flaky test fixes James Clark
2026-11-05 15:49 ` [PATCH 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing James Clark
2026-11-06 5:36 ` sashiko-bot
2026-11-05 15:49 ` [PATCH 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables James Clark
2026-11-06 5:44 ` sashiko-bot [this message]
2026-11-05 15:49 ` [PATCH 3/4] perf test probe_vfs_getname: Fix missing debuginfo detection James Clark
2026-11-06 4:39 ` Namhyung Kim
2026-11-06 5:47 ` sashiko-bot
2026-11-05 15:49 ` [PATCH 4/4] perf test: Don't starve per-process tests with system-wide events James Clark
2026-11-06 4:43 ` Namhyung Kim
2026-11-06 5:51 ` sashiko-bot
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=sashiko-outbox-200850@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=james.clark@linaro.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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