All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: GCC and binutils support for BPF V4 instructions
Date: Fri, 28 Jul 2023 19:06:49 +0200	[thread overview]
Message-ID: <871qgsynh2.fsf@oracle.com> (raw)
In-Reply-To: <CAADnVQLG7WY9BthOQTDQ6UkszJo5HDiGSjKO+jMKaJ+02G90QA@mail.gmail.com> (Alexei Starovoitov's message of "Fri, 28 Jul 2023 09:47:16 -0700")


> On Fri, Jul 28, 2023 at 9:41 AM Jose E. Marchesi
> <jose.marchesi@oracle.com> wrote:
>>
>>
>> Hello.
>>
>> Just a heads up regarding the new BPF V4 instructions and their support
>> in the GNU Toolchain.
>
> Awesome. Thanks for the update!
>
>> V4 sdiv/smod instructions
>>
>>   Binutils has been updated to use the V4 encoding of these
>>   instructions, which used to be part of the xbpf testing dialect used
>>   in GCC.  GCC generates these instructions for signed division when
>>   -mcpu=v4 or higher.
>
> With sdiv/smod implemented do you still have a need for xbpf flag?
> Anything still missing or you can start using -mcpu=v4 in gcc selftests
> and remove xbpf completely?

Just `call %r' (what the clang disassembler calls callx.)

>> So I think we are done with this.  Please let us know if these
>> instructions ever change.
>
> Fingers crossed, they will never change.
> How far are we from running bpf selftests with gcc?

We are getting there, but not quite yet.
See https://gcc.gnu.org/wiki/BPFBackEnd where we track our work.

(The CO-RE builtins entry is basically done, but we are still polishing
 the details before sending the patch to GCC upstream.)
 

  reply	other threads:[~2023-07-28 17:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 16:41 GCC and binutils support for BPF V4 instructions Jose E. Marchesi
2023-07-28 16:47 ` Alexei Starovoitov
2023-07-28 17:06   ` Jose E. Marchesi [this message]
2023-07-28 16:59 ` Yonghong Song
2023-07-28 17:40   ` Jose E. Marchesi
2023-07-28 18:01     ` Jose E. Marchesi
2023-07-28 23:49       ` Alexei Starovoitov
2023-07-29  8:29         ` Jose E. Marchesi
2023-07-29 17:56           ` Alexei Starovoitov
2023-07-30  4:54             ` Jose E. Marchesi
2023-07-30 16:12               ` Yonghong Song
2023-07-30 19:11                 ` Jose E. Marchesi
2023-07-30 16:53               ` Alexei Starovoitov
2023-07-30 21:06                 ` Jose E. Marchesi
2023-07-31 18:10                   ` Alexei Starovoitov

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=871qgsynh2.fsf@oracle.com \
    --to=jose.marchesi@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.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 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.