From: Willy Tarreau <w@1wt.eu>
To: Mats Erik Andersson <mats.andersson64@comhem.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Three if-clauses of constant logic value; char drivers for kernel 2.4.33.3
Date: Sat, 3 Feb 2007 11:07:26 +0100 [thread overview]
Message-ID: <20070203100726.GA1307@1wt.eu> (raw)
In-Reply-To: <1166561978.4133.26.camel@localhost.localdomain>
Hi Mats,
On Tue, Dec 19, 2006 at 09:59:37PM +0100, Mats Erik Andersson wrote:
> Hi there, all masters of kernel code,
>
> I just discovered that the kernel code for 2.4.33.3 contains three
> if-statements that never can change their values, whence they should
> be repaired or eliminated. In source directory linux/drivers/char the
> files vt.c and keyboard.c produce these warning upon compilation:
>
> vt.c:166: varning: comparison is always false due to limited range
> of data type
> vt.c:289: varning: comparison is always false due to limited range
> of data type
> keyboard.c:640: varning: comparison is always true due to limited
> range of data type
>
> I did the compilation with gcc 3.3.5 on Debian Sarge. This behaviour
> appeared first for kernel 2.2.19, since I wanted to revive the old
> minirtl edition, but to my surprise the same warnings appear also
> with the brand new kernel 2.4.33.3.
I've looked at your warnings. They're all totally harmless, and caused
by safety checks against some defines in those functions. While in 2.6,
the two checks in vt.c have been removed, I can't be sure that nobody
in 2.4 changes the defines (eg: embedded systems) in which case the
checks would be totally valid.
So I will leave them. It may look annoying but it's a safe measure IMHO.
Best regards,
Willy
prev parent reply other threads:[~2007-02-03 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 20:59 Three if-clauses of constant logic value; char drivers for kernel 2.4.33.3 Mats Erik Andersson
2006-12-29 22:16 ` Willy Tarreau
2007-02-03 10:07 ` Willy Tarreau [this message]
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=20070203100726.GA1307@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mats.andersson64@comhem.se \
/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