From: David Faust <david.faust@oracle.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] bpf: add v3 atomic instructions
Date: Tue, 25 Jul 2023 15:23:08 -0700 [thread overview]
Message-ID: <3a3df174-da34-be82-c011-aa18cfa27136@oracle.com> (raw)
In-Reply-To: <87zg3j8wjj.fsf@oracle.com>
On 7/25/23 15:18, Jose E. Marchesi wrote:
>
> Hi David.
>
>> +<<<<<<< HEAD
>
> There is a merge problem there.
Ugh, I swear I've fixed this twice now. Yet it keeps cropping up.
Sorry. v2 shortly.
>
>> @opindex mbswap
>> @item -mbswap
>> Enable byte swap instructions. Enabled for CPU v4 and above.
>> @@ -24715,6 +24716,12 @@ Enable byte swap instructions. Enabled for CPU v4 and above.
>> @item -msdiv
>> Enable signed division and modulus instructions. Enabled for CPU v4
>> and above.
>> +=======
>> +@opindex mv3-atomics
>> +@item -mv3-atomics
>> +Enable instructions for general atomic operations introduced in CPU v3.
>> +Enabled for CPU v3 and above.
>> +>>>>>>> 6de76bd11b6 (bpf: add v3 atomic instructions)
next prev parent reply other threads:[~2023-07-25 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 22:08 [PATCH 1/2] bpf: don't print () in bpf_print_operand_address David Faust
2023-07-25 22:08 ` [PATCH 2/2] bpf: add v3 atomic instructions David Faust
2023-07-25 22:18 ` Jose E. Marchesi
2023-07-25 22:23 ` David Faust [this message]
2023-07-25 22:43 ` [PATCH v2 " David Faust
2023-07-26 16:27 ` Jose E. Marchesi
2023-07-25 22:14 ` [PATCH 1/2] bpf: don't print () in bpf_print_operand_address Jose E. Marchesi
2023-07-25 22:23 ` David Faust
2023-07-25 22:49 ` [COMMITTED v2 " David Faust
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=3a3df174-da34-be82-c011-aa18cfa27136@oracle.com \
--to=david.faust@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).