mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Margit Schubert-While <margitsw@t-online.de>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.5.73 compile warnings
Date: Mon, 30 Jun 2003 22:27:52 +0200	[thread overview]
Message-ID: <20030630202752.GJ282@fs.tum.de> (raw)
In-Reply-To: <20030630160319.GA15506@win.tue.nl>

On Mon, Jun 30, 2003 at 06:03:19PM +0200, Andries Brouwer wrote:
> On Mon, Jun 30, 2003 at 05:13:05PM +0200, Margit Schubert-While wrote:
> > 2.5.73 + latest cset
> > GCC 3.3
> > 
> > drivers/char/vt_ioctl.c: In function `do_kdsk_ioctl':
> > drivers/char/vt_ioctl.c:85: warning: comparison is always false due to 
> > limited range of data type
> > drivers/char/vt_ioctl.c:85: warning: comparison is always false due to 
> > limited range of data type
> > drivers/char/vt_ioctl.c: In function `do_kdgkb_ioctl':
> > drivers/char/vt_ioctl.c:211: warning: comparison is always false due to 
> > limited range of data type
> > 
> > drivers/char/keyboard.c: In function `k_fn':
> > drivers/char/keyboard.c:665: warning: comparison is always true due to 
> > limited range of data type
> 
> These are checks of the "cannot happen" type, where "cannot happen"
> can be seen by the compiler, so that it can optimize the tests away.
> 
> As it is now, correctness of the code can be seen locally.
> If the tests are removed, a human reader must look up the values
> of these constants to conclude that the code is correct.

There are cases where a comparison is only on 32 bit architectures 
always true/false (if longs are involved).

There are cases where a #define is set that might be set differently
under certain circumstances:

<--  snip  -->

#define MAX_VALUE 10000

u8 tmp;

if (tmp > MAX_VALUE)
    return -ESOMEERROR;

<--  snip  -->


These are cases where the warning is just noise. But this new warning 
already found several bugs, there are several places where I sent 
patches for things like:

<--  snip  -->

u8 i;

for (i = 0; i <= 0xFF; i++)
    do_something;

<--  snip  -->


In these cases the warning found an actual bug.


Is there any way to tell gcc to disable such warnings locally?


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2003-06-30 20:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-30 15:13 Margit Schubert-While
2003-06-30 16:03 ` Andries Brouwer
2003-06-30 20:27   ` Adrian Bunk [this message]
2003-07-01  7:30 Margit Schubert-While

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=20030630202752.GJ282@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=margitsw@t-online.de \
    /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

all inboxes | Powered by JetHome®