From: Tomas Szepe <szepe@pinerecords.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Paul Jackson <pj@sgi.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disable gcc warnings of sign/unsigned comparison
Date: Fri, 2 Jan 2004 01:59:45 +0100 [thread overview]
Message-ID: <20040102005945.GJ32477@louise.pinerecords.com> (raw)
In-Reply-To: <1073004403.1376.14.camel@nidelv.trondhjem.org>
On Jan-01 2004, Thu, 19:46 -0500
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> P? to , 01/01/2004 klokka 18:15, skreiv Paul Jackson:
>
> > Have you knowledge that more recent versions of gcc don't complain
> > nearly as much of this warning? If so, I will upgrade my gcc and shut
> > up.
>
> I haven't checked with Andrew's '-mm' kernels, but AFAICS I'm not seeing
> any lingering signed/unsigned warnings in the stock 2.6.0 kernel -
> certainly not as many as 1386... (GCC version is latest 3.3.3 prerelease
> from Debian).
I'm not sure, but wasn't this kind of warning moved
from under '-Wall' to under '-W'?
gcc 3.3.2's manpage says:
-W Print extra warning messages for these events:
...
o A comparison between signed and unsigned values
could produce an incorrect result when the signed
value is converted to unsigned. (But don't warn
if -Wno-sign-compare is also specified.)
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2004-01-02 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 12:33 [PATCH] disable gcc warnings of sign/unsigned comparison Paul Jackson
2004-01-01 17:14 ` Trond Myklebust
2004-01-01 23:15 ` Paul Jackson
2004-01-01 23:33 ` Andrew Morton
2004-01-02 0:08 ` Tomas Szepe
2004-01-02 3:20 ` Paul Jackson
2004-01-02 0:46 ` Trond Myklebust
2004-01-02 0:59 ` Tomas Szepe [this message]
2004-01-02 1:31 ` Paul Jackson
2004-01-02 3:05 ` Paul Jackson
[not found] <19ahq-7Rg-11@gated-at.bofh.it>
[not found] ` <19eEs-5lC-15@gated-at.bofh.it>
[not found] ` <19kgS-4HT-19@gated-at.bofh.it>
2004-01-02 1:33 ` Andi Kleen
2004-01-02 3:07 ` Paul Jackson
2004-01-05 1:41 ` Adrian Bunk
2004-01-05 13:16 ` Paul Jackson
2004-03-29 15:44 ` Paul Jackson
2004-03-29 15:43 ` Adrian Bunk
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=20040102005945.GJ32477@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=trond.myklebust@fys.uio.no \
/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