From: Celeste Liu <coelacanthushex@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: "Dmitry V. Levin" <ldv@strace.io>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Guo Ren" <guoren@kernel.org>, "Björn Töpel" <bjorn@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
"David Laight" <David.Laight@ACULAB.COM>,
"Felix Yan" <felixonmars@archlinux.org>,
"Ruizhe Pan" <c141028@gmail.com>,
"Shiqi Zhang" <shiqi@isrc.iscas.ac.cn>,
"Emil Renner Berthing" <emil.renner.berthing@canonical.com>,
"Ivan A. Melnikov" <iv@altlinux.org>
Subject: Re: [PATCH v5] riscv: entry: set a0 = -ENOSYS only when syscall != -1
Date: Thu, 27 Jun 2024 17:35:34 +0800 [thread overview]
Message-ID: <8fb8d780-9e42-438d-88d5-8fe1495cf4d2@gmail.com> (raw)
In-Reply-To: <mvmr0cin6vc.fsf@suse.de>
On 2024-06-27 16:10, Andreas Schwab wrote:
> On Jun 27 2024, Celeste Liu wrote:
>
>> suggestion and we found cast long to ulong is implementation-defined
>> behavior in C
>
> There is nothing implementaton-defined in a long to ulong conversion.
>
Ok, I misremembered. long to ulong is modulo arithmetic but ulong to long
is implementation-defined behavior. There is no type cast issue.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-06-27 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 14:15 [PATCH v5] riscv: entry: set a0 = -ENOSYS only when syscall != -1 Celeste Liu
2023-08-17 15:20 ` patchwork-bot+linux-riscv
2024-06-27 7:14 ` Dmitry V. Levin
2024-06-27 7:47 ` Celeste Liu
2024-06-27 8:10 ` Andreas Schwab
2024-06-27 9:35 ` Celeste Liu [this message]
2024-06-27 9:43 ` Björn Töpel
2024-06-27 9:52 ` Dmitry V. Levin
2024-06-27 10:23 ` Björn Töpel
2024-06-27 10:11 ` Celeste Liu
2024-06-27 10:38 ` Celeste Liu
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=8fb8d780-9e42-438d-88d5-8fe1495cf4d2@gmail.com \
--to=coelacanthushex@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn@rivosinc.com \
--cc=c141028@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=emil.renner.berthing@canonical.com \
--cc=felixonmars@archlinux.org \
--cc=guoren@kernel.org \
--cc=iv@altlinux.org \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@suse.de \
--cc=shiqi@isrc.iscas.ac.cn \
/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