On Fri, 21 Apr 2000 09:49:18 -0400,
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>Stefan Monnier wrote:
>> In the same spirit, I think gcc should automatically get rid of `static'
>> functions which are not called in the file.
>
>Excepting special cases like __initcall and __setup of course
Not to mention this case:
static int do_something(void) {...}
EXPORT_SYMBOL(do_something);
Perfectly legal because of the way that the kernel handles exported
symbols. When compiled with CONFIG_MODULES, 'do_something' can be
accessed from other modules, without CONFIG_MODULES, 'do_something' is
redundant. Do we really want to teach gcc about all the kernel symbol
manipulation? I think not.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:19 EST