This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Final intermodule patch
> Not entirely. You only need to exec one cc1 process, and if you are
> clever enough you may even be able to reuse header file trees. There
> are not very many programs where (a) building takes a long time, and (b)
> "ld -r" is the dominant part of the build cycle. The slowness in GCC is
> coming from the time it takes to generate the .s files.
>
Um... there are plenty of applications where I see this. See recent
postings to the binutils list about IOS recompilations. There you have
_thousands_ of developers recompiling large applications where linking
is the dominant part of the build cycle and building takes a long time.
> > Or would we rule out gcc -c foo.c bar.c -o foobar.o, and maybe accept
> > say gcc -c foo.c -o foo.o -c bar.c -o bar.o?
>
> That would be my preference. I'm not sure about the exact syntax, but
> what I am suggesting is that you get multiple .o files out when you put
> multiple .c files in.
I'm not even sure how you're going to conceptualize doing this...
-eric
--
Eric Christopher <echristo@redhat.com>