public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/10226: unsigned short promotion with bitwise inversion Date: Wed, 26 Mar 2003 22:26:00 -0000 [thread overview] Message-ID: <20030326221600.26541.qmail@sources.redhat.com> (raw) The following reply was made to PR c/10226; it has been noted by GNATS. From: Glen Nakamura <glen@imodulo.com> To: Michael Marks <Michael.Marks@internetmachines.com> Cc: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>, gcc-gnats@gcc.gnu.org Subject: Re: c/10226: unsigned short promotion with bitwise inversion Date: Wed, 26 Mar 2003 12:13:33 -1000 On Wed, Mar 26, 2003 at 01:50:29PM -0800, Michael Marks wrote: > Either is far clearer than the original. > I like the second one better. On second thought, my suggestions won't work for the other comparisons: e.g. <= >= < > != I'm starting to see why it's worded the way it is... > Just one other comment, are both promoted, and are both unsigned after the > promotion. > I thought they are promoted to int. As per you earlier... > > The ~ operator is subject to integer promotion, > so with the implicit conversions the expression becomes: > if ((int) B == ~((int) A)) > which is indeed false in the example above. I think it is promoted to int, but that really doesn't matter since: if ((unsigned int) B == ~((unsigned int) A)) would still be false. The problem is widening an unsigned type and then doing a ~ operation, forces the high bits to 1. In contrast, the other unsigned operand is just widened so the high bits are guaranteed 0. Comparison of these two operands can give unexpected results, which is what the warning is trying to illustrate. - glen
next reply other threads:[~2003-03-26 22:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-26 22:26 Glen Nakamura [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-27 0:16 Michael Marks 2003-03-26 23:06 Falk Hueffner 2003-03-26 22:36 Glen Nakamura 2003-03-26 22:26 Falk Hueffner 2003-03-26 22:06 Michael Marks 2003-03-26 21:56 Falk Hueffner 2003-03-26 21:56 Glen Nakamura 2003-03-26 21:16 Michael Marks 2003-03-26 21:16 ebotcazou 2003-03-26 20:36 Glen Nakamura 2003-03-26 19:56 Michael Marks 2003-03-26 18:26 Falk Hueffner 2003-03-26 18:16 mmarks
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=20030326221600.26541.qmail@sources.redhat.com \ --to=glen@imodulo.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).