From: Paul Jackson <pj@sgi.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: trond.myklebust@fys.uio.no, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disable gcc warnings of sign/unsigned comparison
Date: Thu, 1 Jan 2004 17:31:09 -0800 [thread overview]
Message-ID: <20040101173109.44a58362.pj@sgi.com> (raw)
In-Reply-To: <20040102005945.GJ32477@louise.pinerecords.com>
My suspicion is that Tomas is right - and that something changed in gcc
between 3.3 and 3.3.2, to affectively remove the sign compare warning
from -Wall.
I will look into that more carefully now.
If so, then:
1) The alternative to my patch would be telling everyone to not use
gcc 3.3 or 3.3.1.
2) On the other hand, my patch would still be desirable on the
grounds that it makes gcc 3.3 and 3.3.1 usable for kernel builds,
and is essentially a no-op otherwise, for kernel builds.
I'll post again after I compare some gcc code.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-01-02 1:30 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
2004-01-02 1:31 ` Paul Jackson [this message]
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=20040101173109.44a58362.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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