BPF List
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] Compiled BPF and toolchains
Date: Wed, 21 Feb 2024 12:09:02 +0100	[thread overview]
Message-ID: <87frxm2hwx.fsf@oracle.com> (raw)


The discussions we had last year in LSFMMBPF about BPF support in GCC
were very useful, and led to more and better interactions between the
BPF GCC maintainers, the BPF clang maintainers and the rest of the BPF
community.  This helped a lot to achieve better convergence with clang.

We think it would be good to repeat the experience this year with a
session where we could discuss particular topics related to compiled BPF
in general, like the toolchain requirements introduced by the new
features being proposed for BPF (such as supporting segmented stacks,
just to mention a recent one) and how to better support these in both
GCC and clang.

             reply	other threads:[~2024-02-21 11:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 11:09 Jose E. Marchesi [this message]
2024-02-21 16:32 ` [LSF/MM/BPF TOPIC] Compiled BPF and toolchains 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=87frxm2hwx.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=bpf@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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