From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Will Hawkins <hawkinsw@obs.cr>
Cc: dwarves@vger.kernel.org
Subject: Re: [PATCH 0/1] btf_loader support for subprogram linkage
Date: Mon, 26 Aug 2024 17:00:19 -0300 [thread overview]
Message-ID: <Zsze05ar-q9iKvrS@x1> (raw)
In-Reply-To: <CADx9qWh=Sw2Cr2Y8K_2ExTFJecTrhenN9TzVH0kyKL+buWVa2Q@mail.gmail.com>
On Mon, Aug 26, 2024 at 12:36:45PM -0400, Will Hawkins wrote:
> On Mon, Aug 26, 2024 at 10:58 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > commit ce516fb0cf2a3d9fc45c2a9c7ab2cf4bd24965a0
> > Author: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> > Date: Sun Jul 8 19:47:26 2007 -0300
> > [LIB]: Support DW_AT_MIPS_linkage_name
> > Another C++ specific case:
> > - class TypeTemplate ByName(const string &, size_t);
> > + class TypeTemplate ByName(const string &, size_t); /* linkage=_ZN4ROOT6Reflex12TypeTemplate6ByNameERKSsj */
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
> > So its not really "static" or "stern", but the mangled name in languages
oops, "extern"
> > such as C++, so I think this patch needs reworking, there is ambiguity
> > on the "linkage" term, we should use some other term :-\
>
> Completely understand! I will rework it and propose something different.
>
> I am just thankful that you are so welcoming of the contribution! Your
> enthusiasm has made a contributor for life!
Another recommendation, please don't point the field to strings like
"extern" or "static", as DWARF is not language specific, pahole manages
to handle C mostly, C++ to a great degree but I also used it with Go,
Rust.
We want to make it more language agnostic, so while the "linkage" as a
mangled name is not language specific, "static" or "extern" may be.
So just keep it using the DWARF constant/enumeration, so that at
dwarves_fprintf.c time we can, based on the language encoded in the
debugging info (for BTF we assume C until we introduce some way to
encode Rust (The kernel can be written using Rust, so we're bound to
have something in that direction introduced in BTF at some point)).
- Arnaldo
next prev parent reply other threads:[~2024-08-26 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 21:28 [PATCH 0/1] btf_loader support for subprogram linkage Will Hawkins
2024-08-23 21:28 ` [PATCH 1/1] btf_loader: Support linkages for BTF subprograms Will Hawkins
2024-08-26 7:50 ` Alan Maguire
2024-08-26 14:52 ` [PATCH 0/1] btf_loader support for subprogram linkage Arnaldo Carvalho de Melo
2024-08-26 14:53 ` Arnaldo Carvalho de Melo
2024-08-26 14:58 ` Arnaldo Carvalho de Melo
2024-08-26 16:36 ` Will Hawkins
2024-08-26 20:00 ` Arnaldo Carvalho de Melo [this message]
2024-08-26 20:24 ` Will Hawkins
2024-08-26 14:55 ` Will Hawkins
2024-08-27 4:09 ` [PATCH v2 " Will Hawkins
2024-08-27 14:37 ` Arnaldo Carvalho de Melo
2024-08-27 21:15 ` Will Hawkins
2024-08-27 4:09 ` [PATCH v2 1/1] btf_loader: Support linkages for BTF subprograms Will Hawkins
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=Zsze05ar-q9iKvrS@x1 \
--to=acme@kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=hawkinsw@obs.cr \
/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.