public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@gnu.org>
To: bpf@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] Compiled BPF
Date: Thu, 26 Feb 2026 14:16:15 +0100	[thread overview]
Message-ID: <87tsv3sn2h.fsf@gnu.org> (raw)


Hello people!

[Turns out I forgot to send the topic proposal to the mailing list once
 the topic was proposed (in time) via the google form.  But better late
 than never..]

Work on GCC BPF (also binutils, etc) is progressing at a good pace and
there are a lot of updates and topics that would benefit from having
some face-to-face discussion with the kernel hackers.

Some of these updates and topics are:

- Dealing with some pending differences in behavior between GCC and
  clang/llvm.

- Support of "optional" but important BPF features such as quick calls
  which are currently not supported by GCC.  We are preparing an
  exhaustive support matrix to track this, kees-style.

- Documentation and maintenance of the ABI in general, and some specific
  ABI issues in particular that need agreement and definition at this
  point.

- We are finally ready to add -fverifiable, aiming at GCC 17 (GCC 16 is
  now in stage 4) and we would like to get feedback on some of the
  details.

- Handling CO-RE limitations and corner cases at compile time.  The
  compilers should emit proper diagnostics and behave the same way.

- Testing: we have finally upstreamed the infrastructure that allows
  loading and running GCC BPF tests in kernel.  Along with the support
  for building the kernel BPF selftests, the idea is to have strong
  coverage to detect regressions ASAP in both kernel and compiler side.

- More upstream BPF projects are adding support for using GCC BPF, and
  support in distros is improving.

- We recently got an important reinforcement for the developmet of GCC
  BPF, thanks to Meta: Vineet Gupta, an experienced GCC hacker, has
  joined the party and is already doing great work, speeding up the
  development.

It would be useful if we could have some time during LSFMMBPF to
dedicate to these topics, if possible.

Salud!

             reply	other threads:[~2026-02-26 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 13:16 Jose E. Marchesi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-09  9:20 [LSF/MM/BPF TOPIC] Compiled BPF Jose E. Marchesi
2025-01-09  9:17 Jose E. Marchesi

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=87tsv3sn2h.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --cc=bpf@vger.kernel.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