public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10040: Incorrect warning message for bit fields
Date: Wed, 12 Mar 2003 16:46:00 -0000 [thread overview]
Message-ID: <20030312164600.30564.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/10040; it has been noted by GNATS.
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: <peterson@austin.ibm.com>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: c/10040: Incorrect warning message for bit fields
Date: Wed, 12 Mar 2003 17:40:27 +0100 (CET)
On 12 Mar 2003 peterson@austin.ibm.com wrote:
> int _v: 1;
> if ((*tlb)._hi._v == 1)
>
> warning: comparison is always 0 due to width of bit-field
The warning seems 100% correct to me. The comparison *is* always 0.
> In trying to explain the problem, I'm beginning to see that this error
> message is a result of the bit field being an "int" (signed) rather
> than "unsigned int". In which case, maybe the problem is best
> addressed by a different warning message -- "bit field too small for
> value and sign bit; consider unsigned type for field"
That's too much guessing for my taste. The declaration might be just what
was intended, and only the comparison is bogus. At most I'd consider
"warning: comparison is always 0 due to width and signedness of
bit-field".
Falk
next reply other threads:[~2003-03-12 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 16:46 Falk Hueffner [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 16:45 nathan
2003-03-12 16:26 peterson
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=20030312164600.30564.qmail@sources.redhat.com \
--to=falk.hueffner@student.uni-tuebingen.de \
--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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).