From: Yonghong Song <yonghong.song@linux.dev>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
dwarves@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH dwarves 1/9] dwarf_loader: Reduce parameter checking with clang DW_AT_calling_convention attr
Date: Thu, 19 Mar 2026 10:31:41 -0700 [thread overview]
Message-ID: <4e6b366f-eaea-4cc1-b9c2-629c8089967e@linux.dev> (raw)
In-Reply-To: <abvs73VjXf_1byN6@krava>
On 3/19/26 5:32 AM, Jiri Olsa wrote:
> On Thu, Mar 05, 2026 at 02:55:00PM -0800, Yonghong Song wrote:
>
> SNIP
>
>> ---
>> dwarf_loader.c | 71 +++++++++++++++++++++++++++++++++++++++++++-------
>> dwarves.h | 2 ++
>> 2 files changed, 63 insertions(+), 10 deletions(-)
>>
>> diff --git a/dwarf_loader.c b/dwarf_loader.c
>> index 16fb7be..610b69e 100644
>> --- a/dwarf_loader.c
>> +++ b/dwarf_loader.c
>> @@ -1190,6 +1190,10 @@ static ptrdiff_t __dwarf_getlocations(Dwarf_Attribute *attr,
>> return ret;
>> }
>>
>> +struct func_info {
>> + bool signature_changed;
>> +};
>> +
>> /* For DW_AT_location 'attr':
>> * - if first location is DW_OP_regXX with expected number, return the register;
>> * otherwise save the register for later return
>> @@ -1252,7 +1256,8 @@ out:
>> }
>>
>> static struct parameter *parameter__new(Dwarf_Die *die, struct cu *cu,
>> - struct conf_load *conf, int param_idx)
>> + struct conf_load *conf, int param_idx,
>> + struct func_info *info)
>> {
>> struct parameter *parm = tag__alloc(cu, sizeof(*parm));
>>
>> @@ -1265,6 +1270,8 @@ static struct parameter *parameter__new(Dwarf_Die *die, struct cu *cu,
>> parm->idx = param_idx;
>> if (param_idx >= cu->nr_register_params || param_idx < 0)
>> return parm;
>> + if (cu->producer_clang && !info->signature_changed)
>> + return parm;
> should you check for info != NULL?
We should be okay. I audited that if info is NULL, then param_idx must be < 0.
>
>> /* Parameters which use DW_AT_abstract_origin to point at
>> * the original parameter definition (with no name in the DIE)
>> * are the result of later DWARF generation during compilation
>> @@ -1337,7 +1344,7 @@ static int formal_parameter_pack__load_params(struct formal_parameter_pack *pack
>> continue;
>> }
>>
>> - struct parameter *param = parameter__new(die, cu, conf, -1);
>> + struct parameter *param = parameter__new(die, cu, conf, -1, NULL);
>>
>> if (param == NULL)
>> return -1;
>> @@ -1502,6 +1509,29 @@ static struct ftype *ftype__new(Dwarf_Die *die, struct cu *cu)
>> return ftype;
>> }
>>
> SNIP
>
>> int param_idx = 0;
>> Dwarf_Die child;
>> @@ -2320,7 +2353,7 @@ static int die__process_function(Dwarf_Die *die, struct ftype *ftype,
>> continue;
>> }
>> case DW_TAG_formal_parameter:
>> - tag = die__create_new_parameter(die, ftype, lexblock, cu, conf, param_idx++);
>> + tag = die__create_new_parameter(die, ftype, lexblock, cu, conf, param_idx++, info);
>> break;
>> case DW_TAG_variable:
>> tag = die__create_new_variable(die, cu, conf, 0);
>> @@ -2391,9 +2424,10 @@ out_enomem:
>> static struct tag *die__create_new_function(Dwarf_Die *die, struct cu *cu, struct conf_load *conf)
>> {
>> struct function *function = function__new(die, cu, conf);
>> + struct func_info info = { function->signature_changed };
> would it be easier to add signature_changed to struct ftype or pass
> function pointer directly to die__process_function ?
>
> (after reading the rest of the patches, seems like func_info is needed
> anyway, so maybe not worth it)
Right, there are additional fields in func_info struct.
>
>>
>> if (function != NULL &&
>> - die__process_function(die, &function->proto, &function->lexblock, cu, conf) != 0) {
>> + die__process_function(die, &function->proto, &function->lexblock, cu, conf, &info) != 0) {
>> function__delete(function, cu);
>> function = NULL;
>> }
>> @@ -3045,6 +3079,21 @@ static unsigned long long dwarf_tag__orig_id(const struct tag *tag,
>> return cu->extra_dbg_info ? dtag->id : 0;
>> }
>>
>> +static bool attr_producer_clang(Dwarf_Die *die)
>> +{
>> + Dwarf_Attribute attr;
>> + const char *producer;
>> +
>> + if (dwarf_attr(die, DW_AT_producer, &attr) == NULL)
>> + return false;
>> +
>> + producer = dwarf_formstring(&attr);
>> + if (!producer)
>> + return false;
>> +
> nit you could call attr_string(die, DW_AT_producer, NULL) to get the string
Good point. Will fix it in the next revision.
>
> jirka
>
>> + return !!strstr(producer, "clang");
>> +}
>> +
> SNIP
>
next prev parent reply other threads:[~2026-03-19 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 22:54 [PATCH dwarves 0/9] pahole: Encode true signatures in kernel BTF Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 1/9] dwarf_loader: Reduce parameter checking with clang DW_AT_calling_convention attr Yonghong Song
2026-03-19 12:32 ` Jiri Olsa
2026-03-19 17:31 ` Yonghong Song [this message]
2026-03-05 22:55 ` [PATCH dwarves 2/9] dwarf_loader: Handle signatures with dead arguments Yonghong Song
2026-03-19 18:55 ` Alan Maguire
2026-03-20 5:00 ` Yonghong Song
2026-03-20 19:20 ` Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 3/9] dwarf_loader: Refactor initial ret -1 to be macro PARM_DEFAULT_FAIL Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 4/9] dwarf_laoder: Handle locations with DW_OP_fbreg Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 5/9] dwarf_loader: Change exprlen checking condition in parameter__reg() Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 6/9] dwarf_loader: Detect optimized parameters with locations having constant values Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 7/9] dwarf_loader: Handle expression lists Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 8/9] btf_encoder: Handle optimized parameter properly Yonghong Song
2026-03-05 22:55 ` [PATCH dwarves 9/9] tests: Add a few clang true signature tests Yonghong Song
2026-03-19 18:48 ` Alan Maguire
2026-03-20 4:52 ` Yonghong Song
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=4e6b366f-eaea-4cc1-b9c2-629c8089967e@linux.dev \
--to=yonghong.song@linux.dev \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=olsajiri@gmail.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