All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] disable gcc warnings of sign/unsigned comparison
Date: Thu, 1 Jan 2004 19:07:48 -0800	[thread overview]
Message-ID: <20040101190748.43577763.pj@sgi.com> (raw)
In-Reply-To: <m3pte3i17t.fsf@averell.firstfloor.org>

Andi wrote:
> That was a bug in gcc 3.3.0. It had the -Wsign-compare warning 
> enabled in -Wall by mistake.

Correct.  Even what is now downloadable as:

  ftp://ftp.gnu.org/gnu/gcc/gcc-3.3

seems to have this fixed, and has a gcc/cp/NEWS file entry stating:

     + -Wall no longer implies -W.  The new warning flag, -Wsign-compare,
        included in -Wall, warns about dangerous comparisons of signed and
        unsigned values. Only the flag is new; it was previously part of
        -W.

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

  reply	other threads:[~2004-01-02  3:08 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 [this message]
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
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=20040101190748.43577763.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.