public inbox for bpf@vger.kernel.org
 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
Date: Thu, 09 Jan 2025 10:17:15 +0100	[thread overview]
Message-ID: <87y0zkxs6c.fsf@oracle.com> (raw)


[Resending because I don't think the message reached bpf@vger]

Hello.

I would like to propose an activity for the BPF track at LSFMMBPF.

As in previous editions, the purpose of the activity is to do a quick
recap of the current BPF support in both GCC and clang/LLVM and where we
stand, to discuss and clarify any particular issue that may be relevant
to either compiler, and to collect and address comments, requirements
and other feedback from the kernel hackers present.

On the GCC BPF side we would like to pay special attention to the topic
of divergences, as we are nowadays being bugged not so much by missing
features anymore, as it used to be, but by divergences in the support of
certain features between GCC and clang.  Some of these divergences are
trivial to fix just by following clang's behavior as they are found, but
others require discussion and agreement.  Also, we would like to expand
a bit the scope of the discussion to cover a few topics related to the
"environment" where the compiled BPF programs are built.  Examples of
the later are external linking and the inclusion of host standard
headers by BPF programs.

Thanks!

             reply	other threads:[~2025-01-09  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09  9:17 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
2026-02-26 13:16 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=87y0zkxs6c.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