From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Ihor Solodrai <ihor.solodrai@pm.me>
Cc: Andrew Pinski via Gcc <gcc@gcc.gnu.org>,
bpf <bpf@vger.kernel.org>,
Cupertino Miranda <cupertino.miranda@oracle.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Manu Bretelle <chantra@meta.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Mykola Lysenko <mykolal@fb.com>,
Yonghong Song <yonghong.song@linux.dev>,
David Faust <david.faust@oracle.com>,
Andrew Pinski <pinskia@gmail.com>, Yonghong Song <yhs@fb.com>
Subject: Re: Announcement: GCC BPF is now being tested on BPF CI
Date: Fri, 17 Jan 2025 01:01:02 +0100 [thread overview]
Message-ID: <87zfjqpav5.fsf@oracle.com> (raw)
In-Reply-To: <Yb09J1CvDUk4Mi2bgm3Pd3FJGMi-s3fvc9aftbrOtE4ccqzgwrkalnjKcEA2Y3RB_obEww6EG737pTfyqm6Wyf8fqMRBpaPUA8gH_58GYT4=@pm.me> (Ihor Solodrai's message of "Thu, 16 Jan 2025 22:05:23 +0000")
> As of now, an important missing piece on GCC side is the decl_tags
> support, as they are heavily used by BPF selftests. See a message from
> Yonghong Song:
> https://gcc.gnu.org/pipermail/gcc-patches/2025-January/673841.html
Faust is working on a V2 of that patch series that will be submitted to
gcc-patches soon.
next prev parent reply other threads:[~2025-01-17 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 20:44 Announcement: GCC BPF is now being tested on BPF CI Ihor Solodrai
2025-01-16 22:05 ` Ihor Solodrai
2025-01-16 23:58 ` Jose E. Marchesi
2025-01-17 3:32 ` Ihor Solodrai
2025-01-17 10:44 ` Jose E. Marchesi
2025-01-17 17:55 ` Ihor Solodrai
2025-01-17 18:00 ` Sam James
2025-01-17 0:01 ` Jose E. Marchesi [this message]
2025-01-16 23:59 ` Jose E. Marchesi
2025-01-17 8:33 ` Cupertino Miranda
2025-01-17 17:56 ` Andrii Nakryiko
2025-01-17 13:44 ` Mark Wielaard
2025-01-17 18:09 ` Ihor Solodrai
-- strict thread matches above, loose matches on Subject: below --
2025-01-16 21:49 Sam James
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=87zfjqpav5.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantra@meta.com \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=ihor.solodrai@pm.me \
--cc=mykolal@fb.com \
--cc=pinskia@gmail.com \
--cc=yhs@fb.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