From: Yonghong Song <yonghong.song@linux.dev>
To: Vineet Gupta <vineet.gupta@linux.dev>, dwarves@vger.kernel.org
Cc: bpf@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>,
acme@kernel.org, Alan Maguire <alan.maguire@oracle.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
jose.marchesi@oracle.com, David Faust <david.faust@oracle.com>
Subject: Re: [PAHOLE v4 2/3] dwarf_loader: Add support for DW_TAG_GNU_annotation
Date: Wed, 3 Jun 2026 14:41:11 -0700 [thread overview]
Message-ID: <8ccb6133-2964-450c-9409-ac99e4d5300c@linux.dev> (raw)
In-Reply-To: <20260602195512.1511013-2-vineet.gupta@linux.dev>
On 6/2/26 12:55 PM, Vineet Gupta wrote:
> gcc 16 was the first release to support DW_TAG_GNU_annotations and this
> patch enables the same in pahole. Bulk of changes are dwarf_loader but
> btf_encoder also gains support with minimal changes.
>
> GCC encodes btf_type_tag and btf_decl_tag annotations differently from
> LLVM. While LLVM uses DW_TAG_LLVM_annotation (0x6000) as child DIEs,
> GCC uses DW_TAG_GNU_annotation (0x6001) as standalone sibling DIEs
> referenced via DW_AT_GNU_annotation (0x2139) attributes, with chaining
> through the same attribute on annotation DIEs themselves.
>
> Handle both encoding styles:
>
> For btf_type_tag (pointer annotations):
> - Recognize DW_TAG_GNU_annotation alongside DW_TAG_LLVM_annotation in
> child annotation scanning.
> - Follow DW_AT_GNU_annotation attribute chains on pointer types for
> GCC-style btf_type_tag resolution.
> - Normalize DW_TAG_GNU_annotation to DW_TAG_LLVM_annotation in the
> internal representation so downstream code works unchanged.
>
> For btf_decl_tag (function/struct/member annotations):
> - Add add_gnu_annotation_chain() to follow DW_AT_GNU_annotation
> attribute chains on function, struct, and member DIEs.
> - GCC puts DW_AT_GNU_annotation on the function/struct DIE itself
> (not as child DIEs), referencing sibling annotation DIEs that chain
> via the same attribute.
>
> Also:
> - Silently skip standalone DW_TAG_GNU_annotation DIEs at CU level.
> - Add tag__is_annotation() helper macro for annotation tag checks.
> - Rename add_llvm_annotation -> add_tag_annotation,
> skip_llvm_annotations -> skip_tag_annotations since these now
> handle both LLVM and GNU annotation formats.
>
> Signed-off-by: Vineet Gupta <vineet.gupta@linux.dev>
LGTM except a nit below.
Acked-by: Yonghong Song <yonghong.song@linux.dev>
[...]
> @@ -943,16 +948,40 @@ static int add_child_llvm_annotations(Dwarf_Die *die, int component_idx,
>
> die = &child;
> do {
> - if (dwarf_tag(die) == DW_TAG_LLVM_annotation) {
> - ret = add_llvm_annotation(die, component_idx, conf, head);
> - if (ret)
> - return ret;
> - }
> + if (!die__tag_is_annotation(die))
> + continue;
> +
> + ret = add_tag_annotation(die, component_idx, conf, head);
> + if (ret)
> + return ret;
> } while (dwarf_siblingof(die, die) == 0);
>
> return 0;
> }
>
> +/*
> + * Handle gcc style btf_decl_tag annotations for functions/struct/member tags.
For 'struct', gcc is not supported yet.
> + * Pointers are handled separately, inline in die__create_new_pointer_tag()
> + */
> +static int add_gnu_annotation_chain(Dwarf_Die *die, int component_idx,
> + struct conf_load *conf, struct list_head *head)
> +{
> + Dwarf_Attribute attr;
> + Dwarf_Die annot_die;
> +
> + while (dwarf_attr(die, DW_AT_GNU_annotation, &attr) != NULL &&
> + dwarf_formref_die(&attr, &annot_die) != NULL &&
> + dwarf_tag(&annot_die) == DW_TAG_GNU_annotation) {
> + int ret = add_tag_annotation(&annot_die, component_idx, conf, head);
> + if (ret)
> + return ret;
> +
> + die = &annot_die;
> + }
> +
> + return 0;
> +}
> +
>
[...]
next prev parent reply other threads:[~2026-06-03 21:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 19:55 [PAHOLE v4 1/3] dwarf_loader: Extract die__add_btf_type_tag() helper [NFC] Vineet Gupta
2026-06-02 19:55 ` [PAHOLE v4 2/3] dwarf_loader: Add support for DW_TAG_GNU_annotation Vineet Gupta
2026-06-03 20:08 ` Yonghong Song
2026-06-03 20:54 ` Vineet Gupta
2026-06-03 21:40 ` Yonghong Song
2026-06-17 18:18 ` Vineet Gupta
2026-06-03 20:42 ` Emil Tsalapatis
2026-06-03 21:41 ` Yonghong Song [this message]
2026-06-17 18:34 ` Vineet Gupta
2026-06-07 9:54 ` Alan Maguire
2026-06-17 20:08 ` Vineet Gupta
2026-06-02 19:55 ` [PAHOLE v4 3/3] tests: Support GCC in pfunct-btf-decl-tags test Vineet Gupta
2026-06-03 20:44 ` Emil Tsalapatis
2026-06-03 21:52 ` Yonghong Song
2026-06-03 20:18 ` [PAHOLE v4 1/3] dwarf_loader: Extract die__add_btf_type_tag() helper [NFC] Yonghong Song
2026-06-03 20:37 ` Emil Tsalapatis
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=8ccb6133-2964-450c-9409-ac99e4d5300c@linux.dev \
--to=yonghong.song@linux.dev \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=david.faust@oracle.com \
--cc=dwarves@vger.kernel.org \
--cc=emil@etsalapatis.com \
--cc=jose.marchesi@oracle.com \
--cc=vineet.gupta@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