From: Anders Karlsson <anders@trudheim.com>
To: Riley Williams <Riley@Williams.Name>,
LKML <linux-kernel@vger.kernel.org>
Subject: RE: comparison between signed and unsigned
Date: 04 May 2003 14:15:18 +0100 [thread overview]
Message-ID: <1052054117.31300.13.camel@marx> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCACEFGCKAA.Riley@Williams.Name>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
Hello there Riley,
[snip: compile warnings compare signed to unsigned]
> The obvious question is this: How many of those warnings also occur
> with the pristine source - i.e., the -rc1 without the -ac4 source. It
> would probably be best to wade through the -rc1 sources fixing those
> first, then worry about the -ac* sources once those have been merged
> in.
If I make an estimate, I would say that a great majority of the warnings
are present wether I compile 2.4.20-SuSE, 2.4.21-rc1 or 2.4.21-rc1-ac4.
This seems to be a common (deliberate?) theme throughout parts of the
kernel tree.
I could quite well go through and start fixing things (despite me not
knowing C particularly well) but I would, by someone who knows the
kernel quite well, appreciate an estimate of how likely the result is to
be horribly broken.
As I see it, there might be instances where the comparision between a
signed value and an unsigned value could produce a defect. If people
think this is a good thing to fix and there are people that would accept
patches in normal diff -u format, I could spend some time trying to fix
part of this.
Regards,
/Anders
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2003-05-04 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 9:32 comparision between signed and unsigned Anders Karlsson
2003-05-04 10:15 ` comparison " Riley Williams
2003-05-04 13:15 ` Anders Karlsson [this message]
2003-05-04 16:10 ` comparision " Alan Cox
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=1052054117.31300.13.camel@marx \
--to=anders@trudheim.com \
--cc=Riley@Williams.Name \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.