From: patchwork-bot+linux-riscv@kernel.org
To: Xi Ruoyao <xry111@xry111.site>
Cc: linux-riscv@lists.infradead.org, alex@ghiti.fr,
thomas.weissschuh@linutronix.de, nathan@kernel.org,
Jason@zx2c4.com, paul.walmsley@sifive.com, palmer@dabbelt.com,
guoren@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] RISC-V: vDSO: Correct inline assembly constraints in the getrandom syscall wrapper
Date: Thu, 12 Jun 2025 20:10:31 +0000 [thread overview]
Message-ID: <174975903199.88969.16808687093175866673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250606092443.73650-2-xry111@xry111.site>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@dabbelt.com>:
On Fri, 6 Jun 2025 17:24:44 +0800 you wrote:
> As recently pointed out by Thomas, if a register is forced for two
> different register variables, among them one is used as "+" (both input
> and output) and another is only used as input, Clang would treat the
> conflicting input parameters as undefined behaviour and optimize away
> the argument assignment.
>
> Per an example in the GCC documentation, for this purpose we can use "="
> (only output) for the output, and "0" for the input for that we must
> reuse the same register as the output. And GCC developers have
> confirmed using a simple "r" (that we use for most vDSO implementations)
> instead of "0" is also fine.
>
> [...]
Here is the summary with links:
- [v2] RISC-V: vDSO: Correct inline assembly constraints in the getrandom syscall wrapper
https://git.kernel.org/riscv/c/2b9518684f85
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-06-12 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 2:46 [PATCH v2] RISC-V: vDSO: Wire up getrandom() vDSO implementation Xi Ruoyao
2025-04-11 8:04 ` Thomas Weißschuh
2025-05-23 8:01 ` Alexandre Ghiti
2025-05-23 8:02 ` Xi Ruoyao
2025-05-23 10:06 ` Alexandre Ghiti
2025-06-03 12:48 ` Xi Ruoyao
2025-06-04 11:45 ` Alexandre Ghiti
2025-06-04 15:09 ` [PATCH] RISC-V: vDSO: Correct inline assembly constraints in the getrandom syscall wrapper Xi Ruoyao
2025-06-05 7:15 ` Thomas Weißschuh
2025-06-06 9:24 ` [PATCH v2] " Xi Ruoyao
2025-06-06 9:50 ` Thomas Weißschuh
2025-06-06 22:01 ` Vineet Gupta
2025-06-07 14:16 ` Xi Ruoyao
2025-06-10 7:11 ` Thomas Weißschuh
2025-06-10 8:15 ` Alexandre Ghiti
2025-06-12 20:10 ` patchwork-bot+linux-riscv [this message]
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=174975903199.88969.16808687093175866673.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Jason@zx2c4.com \
--cc=alex@ghiti.fr \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=xry111@xry111.site \
/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®