From: Adrian Bunk <bunk@fs.tum.de>
To: Andi Kleen <ak@muc.de>
Cc: Paul Jackson <pj@sgi.com>, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] disable gcc warnings of sign/unsigned comparison
Date: Mon, 5 Jan 2004 02:41:22 +0100 [thread overview]
Message-ID: <20040105014122.GW10569@fs.tum.de> (raw)
In-Reply-To: <m3pte3i17t.fsf@averell.firstfloor.org>
On Fri, Jan 02, 2004 at 02:33:10AM +0100, Andi Kleen wrote:
> Paul Jackson <pj@sgi.com> writes:
>
> > Right now, compiling a 2.6.0-mm1 (what I had handy) with the 3.3 gcc on
>
> That was a bug in gcc 3.3.0. It had the -Wsign-compare warning
> enabled in -Wall by mistake. Update to gcc 3.3.1, which has this fixed.
Wrong.
It was _not_ a bug in gcc 3.3 .
It was a bug in some _prerelease_ versions of gcc 3.3 SuSE decided to
ship in a release of their distribution.
There is no officially released version of gcc with this problem.
> -Andi
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
next prev parent reply other threads:[~2004-01-05 1:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` [PATCH] disable gcc warnings of sign/unsigned comparison Andi Kleen
2004-01-02 3:07 ` Paul Jackson
2004-01-05 1:41 ` Adrian Bunk [this message]
2004-01-05 13:16 ` Paul Jackson
2004-03-29 15:44 ` Paul Jackson
2004-03-29 15:43 ` Adrian Bunk
2004-01-01 12:33 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
2004-01-02 3:05 ` Paul Jackson
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=20040105014122.GW10569@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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