This is the mail archive of the 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: role of executable_checksum & LTO?

On Tue, 2010-06-29 at 10:22 +0200, David Brown wrote:
> Are you thinking of something like ccache functionality being 
> implemented as a gcc plugin rather than an external program?  You could 
> do many nice things with that that are (I think) impossible with 
> external ccache, such as caching parts of the compilation rather than 
> just the whole compilation.  Pre-compiled headers could be effectively 
> automated by such a system, and if the cache keys were based on internal 
> structures rather than the cpp output (as ccache uses), then the 
> pre-compiled sections could be re-used despite small changes in the code.

Yes, this is an interesting instance of a plugin storing & reloading
data elsewhere. I was not specifically thinking of this, but your
example is a very good illustration of why I believe a checksum or hash
(ie md5sum) identifing the executables is useful.


email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

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