From: sashiko-bot@kernel.org
To: "James Clark" <james.clark@linaro.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v4 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables
Date: Mon, 09 Nov 2026 13:54:00 +0000 [thread overview]
Message-ID: <sashiko-outbox-205038@kernel.org> (raw)
In-Reply-To: <20261109-james-perf-test-fixes-v4-2-355ee6b81917@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/20261109-james-perf-test-fixes-v4-0-355ee6b81917@linaro.org?part=2
next prev parent reply other threads:[~2026-11-09 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 13:48 [PATCH v4 0/4] perf tools: LLVM dwarf and flaky test fixes James Clark
2026-11-09 13:48 ` [PATCH v4 1/4] perf libdw: Find the CU by iterating all CUs when aranges are missing James Clark
2026-11-09 13:56 ` sashiko-bot
2026-11-09 13:48 ` [PATCH v4 2/4] perf dwarf-aux: Support DW_OP_addrx locations for global variables James Clark
2026-11-09 13:54 ` sashiko-bot [this message]
2026-11-09 13:48 ` [PATCH v4 3/4] perf test probe_vfs_getname: Fix missing debuginfo detection James Clark
2026-11-09 13:52 ` sashiko-bot
2026-11-09 13:48 ` [PATCH v4 4/4] perf test: Don't starve per-process tests with system-wide events James Clark
2026-11-09 13:57 ` sashiko-bot
2026-11-09 17:47 ` Ian Rogers
2026-11-10 12:30 ` James Clark
2026-11-10 16:49 ` Ian Rogers
2026-11-11 13:49 ` James Clark
2026-11-09 18:20 ` [PATCH v4 0/4] perf tools: LLVM dwarf and flaky test fixes Ian Rogers
2026-11-10 21:57 ` Namhyung Kim
2026-11-11 19:09 ` (subset) " 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=sashiko-outbox-205038@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 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.