From: Andreas Schwab <schwab@linux-m68k.org>
To: opensbi@lists.infradead.org
Subject: [QUESTION] Usage of negative number notations on unsigned numbers.
Date: Fri, 24 Nov 2023 12:08:49 +0100 [thread overview]
Message-ID: <878r6n76im.fsf@igel.home> (raw)
In-Reply-To: <PN2P287MB0754429FA98AFB8EFD2F4D4BFAB8A@PN2P287MB0754.INDP287.PROD.OUTLOOK.COM> (Karthik B. K.'s message of "Fri, 24 Nov 2023 09:36:07 +0000")
On Nov 24 2023, Karthik B K wrote:
> If so, isn't it safer to use (~0UL) ? This could be a very silent bug. Please correct me if I'm wrong.
The safest way is to write -1 without any suffix. This is guaranteed to
evaluate to the maximum value when converted to any unsigned type.
--
Andreas Schwab, schwab at linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-11-24 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 9:36 [QUESTION] Usage of negative number notations on unsigned numbers Karthik B K
2023-11-24 11:08 ` Andreas Schwab [this message]
2023-11-27 11:59 ` Karthik B K
2023-11-27 12:09 ` Andreas Schwab
2023-11-27 12:55 ` Karthik B K
2023-11-27 13:46 ` Andreas Schwab
2023-11-28 5:28 ` Karthik B K
2023-11-28 6:01 ` Jessica Clarke
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=878r6n76im.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=opensbi@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox