public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/168: Spurious warning in 2.95.2 Date: Tue, 22 Oct 2002 14:56:00 -0000 [thread overview] Message-ID: <20021022215601.24911.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/168; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>, <martin@loewis.home.cs.tu-berlin.de>, <tmwg-gcc@inxservices.com> Cc: Subject: Re: c++/168: Spurious warning in 2.95.2 Date: Tue, 22 Oct 2002 16:48:33 -0500 (CDT) This is equally well a C report as a C++ report, since the problem appears with both languages. The questionably code is ---------------------------------- int main () { unsigned char uc; unsigned short int usi; unsigned int ui; if (uc + usi >= ui); } ---------------------------------- and the report is that this issues an error t.i:5: warning: comparison between signed and unsigned As Jason pointed out, this is due to the fact that the left hand side is converted to an integer. I have no opinion about the validity or the warning, people should use casts to avoid this. I just wanted to share the reduced code. This may be something for value range propagation, since then it would be clear that the left hand side must be positive. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-10-22 21:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-22 14:56 Wolfgang Bangerth [this message] 2002-11-20 18:45 Wolfgang Bangerth
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=20021022215601.24911.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).