Date: Thu, 2 Sep 2004 16:25:45 -0700
From: Andrew Morton <akpm@osdl.org>
To: Tim Bird <tim.bird@am.sony.com>
Cc: bunk@fs.tum.de, ncunningham@linuxmail.org, ak@muc.de,
       linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch]  kill __always_inline
Message-Id: <20040902162545.6b7ae079.akpm@osdl.org>
In-Reply-To: <4137A8E4.9090803@am.sony.com>
References: <20040831221348.GW3466@fs.tum.de>
	<20040831153649.7f8a1197.akpm@osdl.org>
	<20040831225244.GY3466@fs.tum.de>
	<1093993946.8943.33.camel@laptop.cunninghams>
	<20040831163914.4c7c543c.akpm@osdl.org>
	<20040902194600.GE15358@fs.tum.de>
	<4137A8E4.9090803@am.sony.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1122
Lines: 26

Tim Bird <tim.bird@am.sony.com> wrote:
>
> Finally, I think it's bad form to change the meaning of a compiler
> keyword.  It misleading for 'inline' to mean something different
> in the kernel than it does everywhere else.  It means a developer
> can't use standard gcc documentation to understand kernel code, without
> inside knowledge.  This can be painful for casual or new kernel
> developers.

yes, it's horrid.  But until and unless gcc gets fixed, what choice do we
have?  Without this hack, kernel text size increases significantly.

We don't want to have to patch the kernel source in a zillion places for
what is hopefully a temporary problem.  I'd much rather add `--dwim-dammit'
to the gcc command line.

> +#include <linux/compiler.h>	/* for inline weirdness */
>   #include <asm/param.h>

Mozilla white-space-stuffed your patch.  You'll have to use attachments.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/