This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: build gcc with distcc

From: Mike Stump <mrs at apple dot com>
To: Ben Elliston <bje at au1 dot ibm dot com>
Cc: David Fang <fang at csl dot cornell dot edu>, Basile STARYNKEVITCH <basile at starynkevitch dot net>, Weidong Cui <mason dot cui at gmail dot com>, gcc at gcc dot gnu dot org
Date: Mon, 20 Nov 2006 12:42:25 -0800
Subject: Re: build gcc with distcc
References: <20061117073827.GA6674@ours.starynkevitch.net> <20061117030654.N7092-100000@maxwell.csl.cornell.edu> <20061119232616.GA23154@ozlabs.au.ibm.com>

On Nov 19, 2006, at 3:26 PM, Ben Elliston wrote:

No, it records the timestamp of the compiler driver. These would always be different in a bootstrap run, so you would never get any cache hits for second and third stage object files.

If they wanted to do something better, they could use the checksum value instead, the idea is that if you build, cache the results, and them rm -rf and rebuild, all compiles then would come out of the cache.

Follow-Ups:
- Re: build gcc with distcc
  - From: Ben Elliston
- Re: build gcc with distcc
  - From: Paul Brook

References:
- Re: build gcc with distcc
  - From: Basile STARYNKEVITCH
- Re: build gcc with distcc
  - From: David Fang
- Re: build gcc with distcc
  - From: Ben Elliston

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]