From: "Aurélien Aptel" <aaptel@suse.com>
To: linux-sparse@vger.kernel.org
Subject: check idea: warn when mixing signedness in ?: operator (got bitten by this recently)
Date: Mon, 19 Apr 2021 12:21:39 +0200 [thread overview]
Message-ID: <87wnsyzia4.fsf@suse.com> (raw)
Hi,
If the <then> and <else> expression in the ?: ternary operator have
different signedness they will both be implicitely casted to unsigned.
When the result is stored in a variable with a storage capable of
holding both values, this is very unexpected. Consider this example:
int rc = -1;
unsigned int foo = 123;
long x = y ? foo : rc;
If one of the branch of the ?: is unsigned, then the compiler will cast
both branch to unsigned _before_ storing it in x. Despite long being
able to store INT_MIN, INT_MAX, UINT_MAX (assuming 64b long/32b int).
So if y is 0, it's basically doing
long x = (long)((unsigned int)-1);
Which will result in storing 0x00000000ffffffff (4294967295) instead of
expected 0xffffffffffffffff (-1).
I thought we hit some sort of weird compiler bug but after reducing the
problem to the simple example above and trying it GCC, clang, ICC and
MSVC they all do the same thing: https://godbolt.org/z/P5Ts7o1df
So it is most likely a C quirk. Standard reads 6.5.15. 5)
> If both the second and third operands have arithmetic type, the result
> type that would be determined by the usual arithmetic conversions, were
> they applied to those two operands, is the type of the result.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
next reply other threads:[~2021-04-19 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 10:21 Aurélien Aptel [this message]
2021-04-19 22:00 ` check idea: warn when mixing signedness in ?: operator (got bitten by this recently) Luc Van Oostenryck
2021-04-20 12:16 ` Dan Carpenter
2021-04-20 12:44 ` Aurélien Aptel
2021-04-21 10:30 ` Dan Carpenter
2021-04-21 13:43 ` Aurélien Aptel
2021-04-21 13:46 ` Dan Carpenter
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=87wnsyzia4.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-sparse@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.