From: Dave Jones <davej@codemonkey.org.uk>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Art Haas <ahaas@airmail.net>, linux-kernel@vger.kernel.org
Subject: Re: Latest GCC-3.3 is much quieter about sign/unsigned comparisons
Date: Mon, 5 May 2003 14:06:41 +0100 [thread overview]
Message-ID: <20030505130641.GA13082@suse.de> (raw)
In-Reply-To: <20030505074803.GA1775@louise.pinerecords.com>
On Mon, May 05, 2003 at 09:48:04AM +0200, Tomas Szepe wrote:
> > ... has eliminated all the warnings that GCC-3.3 by default printed
> > with regards to signed/unsigned comparisons. A build of today's BK
> > with this compiler is much quieter than those previously done
> > with the 3.3 snapshots.
>
> Is this a good thing, though? I'm quite sure those warnings were useful.
In a lot of cases, they were just noise. They are still there with
-W if you really want to see them.
Dave
prev parent reply other threads:[~2003-05-05 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 21:22 Latest GCC-3.3 is much quieter about sign/unsigned comparisons Art Haas
2003-05-05 6:23 ` Anders Karlsson
2003-05-05 14:20 ` Jörn Engel
2003-05-05 7:48 ` Tomas Szepe
2003-05-05 13:06 ` Dave Jones [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=20030505130641.GA13082@suse.de \
--to=davej@codemonkey.org.uk \
--cc=ahaas@airmail.net \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.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