public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org, Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Subject: Re: proposal: remove unused macros
Date: Mon, 13 Nov 2006 21:29:17 -0800	[thread overview]
Message-ID: <20061113212917.3c5b8317.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200611132119.17858.gene.heskett@verizon.net>

On Mon, 13 Nov 2006 21:19:17 -0500 Gene Heskett wrote:

> On Monday 13 November 2006 13:13, Mariusz Kozlowski wrote:
> >Hello,
> >
> >	Recently someone send a patch that fixed some old '#ifdef'ed code with
> > syntax error (stray brackets). The broken code was there for a long
> > time and nobody saw that. I digged some more and wrote a simple program
> > that counted '(' and ')' in the kernel code that emits apropriate text
> > if for a given file both numbers differ. That is probably dumb idea but
> > it worked :-) Quite fast I found a dozen of broken macros with syntax
> > errors etc. All of those macros are unused. I digged a bit deeper and
> > used '-Wunused-macros' flag which with causes 8340 new warnings to be
> > emited for 2.6.19-rc5-mm1 with 'allmodconfig'. For sure there are false
> > positives (see gcc man page) but even if i.e. 50% of them are fp then
> > we still have around 4k of unused macros scattered around the tree.
> >
> >To me this is a dead code. I can review the code causing these warnings
> > and prepare patches 'per subsystem' or whatever to address this issue.
> > That is if nobody opposes.
> 
> With regard to your parens checking code, I re-wrote from a broken 
> version, about 20 years ago, a utility to check all that.  I used it on 
> the coco/os9 systems at the time, then built it for the amiga, and 
> rebuilt it for linux a few years back.  It checks brackets, quotes in " 
> style and ' style and ;, etc stuff.  I called mine cntx, and I've used it 
> occasionally here, but haven't had the need/urge to test any kernel code 
> with it so far.
> 
> If anyone is interested, and the list will take attachments of that 
> nature, I'd be honored to share it.  What say you all?

I'm interested.

Thanks,
---
~Randy

  reply	other threads:[~2006-11-14  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-13 18:13 proposal: remove unused macros Mariusz Kozlowski
2006-11-14  2:19 ` Gene Heskett
2006-11-14  5:29   ` Randy Dunlap [this message]
2006-11-14 11:18   ` Horst H. von Brand
2006-11-14 14:29     ` Gene Heskett
2006-11-14 14:37       ` Mariusz Kozlowski

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=20061113212917.3c5b8317.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.kozlowski@tuxland.pl \
    /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