All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disable gcc warnings of sign/unsigned comparison
Date: Thu, 1 Jan 2004 19:20:49 -0800	[thread overview]
Message-ID: <20040101192049.59dd7747.pj@sgi.com> (raw)
In-Reply-To: <20040101153303.75d37307.akpm@osdl.org>

Andrew wrote:
> ugh, that is unacceptable.
> Unless anyone has a better idea, yes, we should apply your patch.

It seems that the only place I can find the gcc with this bug (that
-Wall implies -Wsign-compare) is the gcc 3.3 that came with my SuSE
Linux 8.2 distribution.  Each of the 3.3, 3.3.1 and 3.3.2 versions
available at ftp.gnu.org/gnu/gcc are ok - no such bug.

So it's not a big deal either way whether to apply this patch.

  In the short term, it helps a very specific version of gcc.

  In the longer term, it clutters the top Makefile with a pimple
  to address a transient glitch.

  Technically it is a no-op for other gcc versions, since
  sign-compare is off in all other cases anyway.

I vote that you:

  ==> Drop my patch in the trash

in the interests of avoiding Makefile clutter.  Tell people like
me that if it hurts to use this gcc 3.3, then don't use it ;).

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

  parent reply	other threads:[~2004-01-02  3:20 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 [this message]
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
     [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=20040101192049.59dd7747.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.