From: Vivian Wang <wangruikang@iscas.ac.cn>
To: Yury Norov <yury.norov@gmail.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Charlie Jenkins" <charlie@rivosinc.com>,
"Xiao Wang" <xiao.w.wang@intel.com>,
"Christoph Müllner" <christoph.muellner@vrull.eu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"Vivian Wang" <uwu@dram.page>
Subject: Re: [PATCH v2 4/5] riscv: bitops: Use __riscv_has_extension_likely
Date: Fri, 22 Aug 2025 01:49:16 +0800 [thread overview]
Message-ID: <871ca57a-2f0a-4b21-be8f-7a26a76fd58d@iscas.ac.cn> (raw)
In-Reply-To: <4dba27c4-e7a5-4ffc-8073-08a83c68e527@iscas.ac.cn>
On 8/22/25 01:46, Vivian Wang wrote:
> [...]
>
> And, codegen-wise:
>
> ALTERNATIVE("j %l[no_alt]", "nop", ...) -> likely() ALTERNATIVE("nop",
> "j %l[has_alt]", ...) -> unlikely()
>
I messed up the formatting, should be:
ALTERNATIVE("j %l[no_alt]", "nop", ...) -> likely()
ALTERNATIVE("nop", "j %l[has_alt]", ...) -> unlikely()
Vivian "dramforever" Wang
next prev parent reply other threads:[~2025-08-21 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 9:16 [PATCH v2 0/5] riscv: Use __riscv_has_extension_{likely,unlikely} Vivian Wang
2025-08-21 9:16 ` [PATCH v2 1/5] riscv: pgtable: Use __riscv_has_extension_unlikely Vivian Wang
2025-08-21 9:16 ` [PATCH v2 2/5] riscv: checksum: Use __riscv_has_extension_likely Vivian Wang
2025-08-21 9:16 ` [PATCH v2 3/5] riscv: hweight: " Vivian Wang
2025-08-21 9:16 ` [PATCH v2 4/5] riscv: bitops: " Vivian Wang
2025-08-21 14:44 ` Yury Norov
2025-08-21 17:46 ` Vivian Wang
2025-08-21 17:49 ` Vivian Wang [this message]
2025-08-27 3:48 ` Yury Norov
2025-08-27 7:07 ` Vivian Wang
2025-08-21 9:16 ` [PATCH v2 5/5] riscv: cmpxchg: " Vivian Wang
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=871ca57a-2f0a-4b21-be8f-7a26a76fd58d@iscas.ac.cn \
--to=wangruikang@iscas.ac.cn \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=christoph.muellner@vrull.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@rasmusvillemoes.dk \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=uwu@dram.page \
--cc=xiao.w.wang@intel.com \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®