From: patchwork-bot+netdevbpf@kernel.org
To: Cupertino Miranda <cupertino.miranda@oracle.com>
Cc: bpf@vger.kernel.org, andrii.nakryiko@gmail.com,
yonghong.song@linux.dev, eddyz87@gmail.com,
alexei.starovoitov@gmail.com, david.faust@oracle.com,
jose.marchesi@oracle.com
Subject: Re: [PATCH v2 bpf-next] libbpf: add support to GCC in CORE macro definitions
Date: Tue, 13 Feb 2024 19:40:30 +0000 [thread overview]
Message-ID: <170785323033.16134.4475272319728217015.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240213173543.1397708-1-cupertino.miranda@oracle.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 13 Feb 2024 17:35:43 +0000 you wrote:
> Due to internal differences between LLVM and GCC the current
> implementation for the CO-RE macros does not fit GCC parser, as it will
> optimize those expressions even before those would be accessible by the
> BPF backend.
>
> As examples, the following would be optimized out with the original
> definitions:
> - As enums are converted to their integer representation during
> parsing, the IR would not know how to distinguish an integer
> constant from an actual enum value.
> - Types need to be kept as temporary variables, as the existing type
> casts of the 0 address (as expanded for LLVM), are optimized away by
> the GCC C parser, never really reaching GCCs IR.
>
> [...]
Here is the summary with links:
- [v2,bpf-next] libbpf: add support to GCC in CORE macro definitions
https://git.kernel.org/bpf/bpf-next/c/12bbcf8e840f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-13 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 17:35 [PATCH v2 bpf-next] libbpf: add support to GCC in CORE macro definitions Cupertino Miranda
2024-02-13 19:40 ` patchwork-bot+netdevbpf [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=170785323033.16134.4475272319728217015.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=jose.marchesi@oracle.com \
--cc=yonghong.song@linux.dev \
/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