public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anders Karlsson <anders@trudheim.com>
To: Art Haas <ahaas@airmail.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Latest GCC-3.3 is much quieter about sign/unsigned comparisons
Date: 05 May 2003 07:23:01 +0100	[thread overview]
Message-ID: <1052115781.25951.43.camel@marx> (raw)
In-Reply-To: <20030504212256.GE24907@debian>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Hello there, :-)

On Sun, 2003-05-04 at 22:22, Art Haas wrote:
> Hi.
> 
> This change ...
> 
> 2003-05-02  Zack Weinberg  <zack@codesourcery.com>
> 
> 	PR c/10604
> 	* c-opts.c (c_common_decode_option <OPT_Wall>): Set
> 	warn_sign_compare for C++ only.
> 	* doc/invoke.texi: Clarify documentation of -Wsign-compare.
> 
> ... 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.

Yes, it means the warnings are not printed, it doesn't mean the problem
has gone away though.

I'd still like for someone to tell me if there is a specific reason to
use signed numbers in for example inode.c in one of the filesystems
(can't remember which one of the top of my head). I for one would get
rather surprised if some of my data started getting stored with negative
inodes...

Regards,

/Anders


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2003-05-05  6:10 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 [this message]
2003-05-05 14:20   ` Jörn Engel
2003-05-05  7:48 ` Tomas Szepe
2003-05-05 13:06   ` Dave Jones

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=1052115781.25951.43.camel@marx \
    --to=anders@trudheim.com \
    --cc=ahaas@airmail.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox