xfs
[Top] [All Lists]

Re: Warnings when compiling xfs_macros.c

To: Craig Rodrigues <rodrigc@xxxxxxxxxxxxxx>
Subject: Re: Warnings when compiling xfs_macros.c
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 8 Sep 2005 15:38:57 +0100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20050908143500.GA48023@xxxxxxxxxxxxxx>
References: <20050907174535.GA1850@xxxxxxxxxxxxxx> <20050907182059.GA13074@xxxxxxxxxxxxx> <20050907184542.GA2316@xxxxxxxxxxxxxx> <20050908105745.GA5847@xxxxxxxxxxxxx> <43204609.60203@xxxxxxx> <20050908143500.GA48023@xxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
On Thu, Sep 08, 2005 at 10:35:00AM -0400, Craig Rodrigues wrote:
> On Thu, Sep 08, 2005 at 09:09:13AM -0500, Steve Lord wrote:
> > If someone converts all the code to plain macros, I suggest you look
> > carefully at the ones which default to being functions, these are
> > probably the main culprits when it comes to code bloat. With today's
> > fast cpus, keeping them as functions might still be worth while
> > from a code size point of view.
> 
> Well, this type of code cleanup is probably a good thing to do,
> but is not what I want to tackle yet for my short-term goal
> of getting xfs_macros.c to compile without warning if
> -Wmissing-prototypes is added to the gcc flags (as is done
> during a FreeBSD kernel build).

But we're not really looking for half-backed things.  -Wmissing-prototypes
is a rather stupid warnings extension, and if you care for it you'll have
to deal with it in your tree.  If you on the other hands do a cleanup that
fixes your problems as side-effects that's of course fine.


<Prev in Thread] Current Thread [Next in Thread>