From: Adrian Bunk <bunk@fs.tum.de>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Andrew Morton <akpm@osdl.org>, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move some more intilization out of drivers/char/mem.c
Date: Mon, 22 Sep 2003 13:13:49 +0200 [thread overview]
Message-ID: <20030922111349.GO6325@fs.tum.de> (raw)
In-Reply-To: <20030921075430.GA4938@actcom.co.il>
On Sun, Sep 21, 2003 at 10:54:30AM +0300, Muli Ben-Yehuda wrote:
> On Sat, Sep 20, 2003 at 11:48:53PM -0700, Andrew Morton wrote:
> > Christoph Hellwig <hch@lst.de> wrote:
> > >
> > > > Please compile-test things...
> > >
> > > Well, I compiled this here. I see, looks like I lost half of the patch
> > > when sending it to you. Sorryh for that, here's the full patch:
> >
> > It still generates warnings. I suggest you build kernels with a script
> > which saves up stderr and spits it all out at the end. That way, these
> > things are noticed.
>
> This might be a good time to recommend -Werror. Last time it came up
> (http://marc.theaimsgroup.com/?l=linux-kernel&m=102654562025374&w=2),
> Alan was dead set against it, and Linus did not apply it, but did
> think it had some merit
> (http://marc.theaimsgroup.com/?l=linux-kernel&m=102658611213914&w=2).
>
> Compiling 2.6.0-t5-cvs with my .config and -Werror uncovered only two
> warnings. Patches sent seperately.
>...
In 2.6, warnings are very visible, and many people are working on
reducing the number of warning.
A full build of 2.6 gives between 200 and 300 warnings with gcc 3.3
including harmless ones.
You get several "unused variable" warnings when you disable e.g.
CONFIG_PROC_FS.
When compiling with a different compiler version (e.g. 2.95) you get a
similar number of warnings, but different warnings.
Some warnings are the fault of gcc (and noone will fix gcc 2.95 or the
unofficial gcc 2.96).
Adding -Werror will turn into a maintenance nightmare.
> Muli Ben-Yehuda
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2003-09-22 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 13:29 [PATCH] move some more intilization out of drivers/char/mem.c Christoph Hellwig
2003-09-20 23:06 ` Andrew Morton
2003-09-21 6:30 ` Christoph Hellwig
2003-09-21 6:48 ` Andrew Morton
2003-09-21 7:05 ` Christoph Hellwig
2003-09-21 17:03 ` Randy.Dunlap
2003-09-21 7:54 ` Muli Ben-Yehuda
2003-09-22 11:13 ` Adrian Bunk [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=20030922111349.GO6325@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.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.