Re: ccache-3 upgrade

----- Original Message ----- 
From: "Olaf Westrik" <weizen_42-Yz37vSk3/[email protected]>
To: "Gilles Espinasse" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, February 09, 2011 6:40 AM
Subject: Re: [IPCop-devel] ccache-3 upgrade


> On 2011-01-24 08:54, Gilles Espinasse wrote:
>
> > Probably much easier to use a separate log file for ccache stats
> > Attached the changed Config (and simplified a bit as we don't need to
check
> > if ccache is present after toolchain)
>
>
> Using 1 log for toolchain and normal build, can produce result like this:
>
> ...
>
> /home/svn/ipcop/test/trunk/files_i486/01_toolchain/strip
> cache directory                     /home/svn/ipcop/test/trunk/ccache
> cache hit (direct)                     0
> cache hit (preprocessed)               0
> cache miss                             0
> files in cache                     39467
> cache size                         420.0 Mbytes
> max cache size                       1.5 Gbytes
> /usr/src/files_i486/02_base/stage2
> cache directory                     /usr/src/ccache
> cache hit (direct)                     0
> cache hit (preprocessed)               0
> cache miss                             0
> files in cache                     74775
> cache size                         565.6 Mbytes
> max cache size                       1.0 Gbytes
>
> ...
>
> As the ccache from toolchain build could be some time ago or even on
> another machine, normally has no relation to the 'actual' ccache
> contents, I think it better to separate the logs.
>
I think that log should not be include in toolchain package.
I know I have some fixes to do for that.
I would to always be able to repackage the toolchain but I have to care not
include some files.

>
> Other (minor) point is the ccache size. When using prepackaged toolchain
> the size is left as default. Should be OK though as without toolchain
> build the ccache size requirement is not so high.
>
>
> Olaf

Yes that true that default size should be enought if you don't build the
toolchain.
We could notice in stage2 to add a ccache call if we compile much more
package (I hope not).

Gilles


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb