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++/1056: spurious warning on implicit conversion followed by promotion and comparison Date: Sun, 10 Nov 2002 13:16:00 -0000 [thread overview] Message-ID: <20021110211601.24347.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/1056; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/1056: spurious warning on implicit conversion followed by promotion and comparison Date: Sun, 10 Nov 2002 15:16:47 -0600 (CST) This report is about this code: --------------------------------------- struct X { operator unsigned short () const; }; int main() { X s; unsigned long l; if (l == s); if (s == l); return 0; } ------------------------------ and the following warnings: tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/gcc -W -Wall -c x.cc x.cc: In function `int main()': x.cc:9: warning: comparison between signed and unsigned integer expressions x.cc:10: warning: comparison between signed and unsigned integer expressions I had initially thought that this may be due to argument promotion to a signed type from the unsigned short the conversion operator returns, but then the same should happen when we define "s" as an unsigned short right from the start. However, this makes the warning go away. So I don't know... W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-10 21:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-10 13:16 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-20 18:53 Wolfgang Bangerth 2001-08-12 9:28 lerdsuwa
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=20021110211601.24347.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).