All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, bpf@vger.kernel.org
Cc: elena.zannoni@oracle.com
Subject: Re: Compiler support for BPF at LSFMMBPF 2025 - Is there interest?
Date: Wed, 8 Jan 2025 12:28:09 -0800	[thread overview]
Message-ID: <93955687-a82b-4365-931c-d53ecd1dacd7@linux.dev> (raw)
In-Reply-To: <87ikqpmf81.fsf@oracle.com>




On 1/8/25 8:40 AM, Jose E. Marchesi wrote:
> Hello people.
>
> The deadline is approaching and we were wondering, should we prepare a
> proposal for a discussion around BPF support in both GCC and clang for
> LSFMMBPF?  Like in previous years, we could do a recap of the on-going
> work and where we stand, and discuss and clarify particular issues.

Thanks. Indeed this is a good topic to discuss w.r.t. clang/gcc related 
issues.



      parent reply	other threads:[~2025-01-08 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08 16:40 Compiler support for BPF at LSFMMBPF 2025 - Is there interest? Jose E. Marchesi
2025-01-08 17:10 ` Alexei Starovoitov
2025-01-08 17:23   ` Jose E. Marchesi
2025-01-08 20:28 ` Yonghong Song [this message]

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=93955687-a82b-4365-931c-d53ecd1dacd7@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=bpf@vger.kernel.org \
    --cc=elena.zannoni@oracle.com \
    --cc=jose.marchesi@oracle.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.