Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine

Sam Ravnborg
2006-08-25T07:21:58Z

On Fri, Aug 25, 2006 at 08:01:27AM +0200, Jan Engelhardt wrote:
> >> Compiling files on their own (`make drivers/foo/bar.o`) seems to make
> >> the optimization void. Sure, most people don't stop compiling in
> >> between. Just a note
> >
> >Actually I'm not entirely sure what you write is true. It'll _build_
> >fs/jffs2/read.o, for example, but it still won't then use it when I make
> >the kernel -- it'll just use fs/jffs2/jffs2.o which is built from all
> >the C files with --combine. So the optimisation isn't lost.
>
> Umm then it spends double the time in compilation, doing:
>
> read.o <- read.c
It will only do this if you ask for it.
The question was what happened when you did make read.o

> foo.o <- foo.c
> bar.o <- bar.c
> built-in.o <- read.c foo.c bar.c
>
> (cf. default current:
> built-in.o <- read.o foo.o bar.o)

And this discussion is btw. mood. If the general opinion is that we shall
include the -combine support all the kbuild infrastructure will anyway
be redone.
There are several small things that are not addressed in todays
implementation and that will be fixed one way or the other.

Sam