From: Yonghong Song <yonghong.song@linux.dev>
To: Cupertino Miranda <cupertino.miranda@oracle.com>, bpf@vger.kernel.org
Subject: Re: [PATCH 0/3] Correct recent GCC incompatible changes.
Date: Tue, 20 Aug 2024 12:42:53 -0700 [thread overview]
Message-ID: <6c07765b-952f-4132-aa99-b31010eea598@linux.dev> (raw)
In-Reply-To: <20240819151129.1366484-1-cupertino.miranda@oracle.com>
On 8/19/24 8:11 AM, Cupertino Miranda wrote:
> Hi everyone,
>
> Apologies for the previous patches which did not include a cover letter.
> My wish was to send 3 indepepdent patches but after the initial mistake lets keep
> this as a series although they are all independent from themselves.
>
> The changes in this patch series is related to recovering GCC support to
> build the selftests.
> A few tests and a makefile change have broken the support for GCC in the
> last few months.
Cupertino, it would be great if we can speed up to add CI test with gcc-bpf, even
just for compilation only.
next prev parent reply other threads:[~2024-08-20 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 15:11 [PATCH 0/3] Correct recent GCC incompatible changes Cupertino Miranda
2024-08-19 15:11 ` [PATCH 1/3] selftests/bpf: Disable strict aliasing for verifier_nocsr.c Cupertino Miranda
2024-08-19 15:11 ` [PATCH 2/3] selftest/bpf: _GNU_SOURCE redefined in g++ Cupertino Miranda
2024-08-19 22:29 ` Andrii Nakryiko
2024-08-19 15:11 ` [PATCH 3/3] selftest/bpf: Adapt inline asm operand constraint for GCC support Cupertino Miranda
2024-08-19 22:50 ` [PATCH 0/3] Correct recent GCC incompatible changes patchwork-bot+netdevbpf
2024-08-20 19:42 ` Yonghong Song [this message]
2024-08-22 17:02 ` Cupertino Miranda
2024-08-22 17:32 ` Yonghong Song
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=6c07765b-952f-4132-aa99-b31010eea598@linux.dev \
--to=yonghong.song@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox