mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disable gcc warnings of sign/unsigned comparison
Date: Thu, 01 Jan 2004 19:46:44 -0500	[thread overview]
Message-ID: <1073004403.1376.14.camel@nidelv.trondhjem.org> (raw)
In-Reply-To: <20040101151516.236cb610.pj@sgi.com>

På to , 01/01/2004 klokka 18:15, skreiv Paul Jackson:

> Have you knowledge that more recent versions of gcc don't complain
> nearly as much of this warning?  If so, I will upgrade my gcc and shut
> up.

I haven't checked with Andrew's '-mm' kernels, but AFAICS I'm not seeing
any lingering signed/unsigned warnings in the stock 2.6.0 kernel -
certainly not as many as 1386... (GCC version is latest 3.3.3 prerelease
from Debian).

You mentioned Richard Gooch's name cropping up in the broken code, does
that perhaps mean devfs? If so then the warnings may just reflect the
fact that this code has been unmaintained for too long (devfs has after
all been marked as "obsolete").

Cheers,
   Trond

  parent reply	other threads:[~2004-01-02  0:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=1073004403.1376.14.camel@nidelv.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --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
all inboxes | Powered by JetHome®