From: Dodji Seketeli <dodji@seketeli.org>
To: "Matthias Männich" <maennich@google.com>
Cc: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>,
Giuliano Procida <gprocida@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
elena.zannoni@oracle.com,
clang-built-linux <llvm@lists.linux.dev>
Subject: Re: Kernel ABI Monitoring and toolchain support
Date: Thu, 23 Jun 2022 13:54:57 +0200 [thread overview]
Message-ID: <87edzffvce.fsf@seketeli.org> (raw)
In-Reply-To: <CAJFNNnoWDS547q-MDye4L_2WkT9odxAvhD2JQkALH7Erm2YJtQ@mail.gmail.com> ("Matthias Männich"'s message of "Mon, 20 Jun 2022 14:42:31 +0100")
Matthias Männich <maennich@google.com> a écrit:
> Hi!
>
> That is a very late response, sorry about that.
>
> In the Android MC we will have a talk about the latest news monitoring
> Android Kernel ABIs already, but I definitely see value in a more
> generic session in the Kernel+Toolchain MC. Is that schedule already
> finalized or is there still a slot available and interest from your
> side?
>
> In particular, I would be interested in discussing ways to standardize
> ABI and type information in a way that it can be embedded into
> binaries in a less ambiguous way. In other words, what can we do to
> not rely entirely on intermediate formats like CTF or DWARF to make
> sense of an ABI? Maybe CTF is already a good starting point, yet some
> additions are needed (e.g. other language features like for C++)?
I'd be super interested in this topic, for what it's worth. I won't be
able to attend the conference physically, though, only remotely.
Would that work?
Thanks.
--
Dodji
next prev parent reply other threads:[~2022-06-23 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 21:33 Kernel ABI Monitoring and toolchain support Nick Desaulniers
2022-04-20 16:02 ` Jose E. Marchesi
[not found] ` <CAGvU0H=sjwsWEmq1R7LKHiPjB3aBkzQ_qJqXDxhT_rFJShgVFg@mail.gmail.com>
2022-05-07 2:15 ` Guillermo E. Martinez
2022-06-20 13:42 ` Matthias Männich
2022-06-21 21:19 ` Nick Desaulniers
2022-06-21 21:27 ` Elena Zannoni
2022-06-22 2:14 ` Guillermo E. Martinez
2022-06-22 15:27 ` Guillermo E. Martinez
2022-06-22 19:47 ` Nick Desaulniers
2022-06-23 11:54 ` Dodji Seketeli [this message]
2022-06-24 9:03 ` Dodji Seketeli
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=87edzffvce.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=elena.zannoni@oracle.com \
--cc=gprocida@google.com \
--cc=guillermo.e.martinez@oracle.com \
--cc=llvm@lists.linux.dev \
--cc=maennich@google.com \
--cc=ndesaulniers@google.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 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.