Subject: Re: proposal: libcc1 -> static
To: richard.earnshaw@arm.com, Ian Dall <Ian.Dall@dsto.defence.gov.au>
From: Ignatios Souvatzis <is@jocelyn.rhein.de>
List: tech-toolchain
Date: 01/05/1999 21:13:05
On Tue, Jan 05, 1999 at 10:27:15AM +0000, Richard Earnshaw wrote:
>
> > > It's only when you heavily mix languages that you get a speedup with the
> > > shared object, and then, it's not much of a speedup.
> >
> > With static linking there will be no sharing of pages between cc1, as
> > and ld which you might want if you are using the -pipe option.
> >
> > However, I don't really think -pipe is very good anyway and instead
> > avoid disk traffic by making TMPDIR a memory file system.
> >
>
> There is nothing in libcc1 that as or ld will use. The only page sharing
> would be between cc1 cc1plus f771 and cc1obj, which are never used by the
> simultaneously for a single compilation. Hence this has nothing to do
> with making -pipe work more efficiently.
it will make -j$N jobs (parallel compiling) share more, potentially.
-is