From: Sam Ravnborg <sam@ravnborg.org>
To: Roland McGrath <roland@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild vs ccache
Date: Thu, 8 Jan 2009 06:42:15 +0100 [thread overview]
Message-ID: <20090108054215.GA11628@uranus.ravnborg.org> (raw)
In-Reply-To: <20090108040336.28B10FC3E0@magilla.sf.frob.com>
On Wed, Jan 07, 2009 at 08:03:36PM -0800, Roland McGrath wrote:
>
> make clean; ccache -s > before-`git describe`; make -j9; ccache -s > after-`git describe`; diff -u {before,after}-`git describe`
>
> v2.6.28:
>
> -cache hit 737661
> -cache miss 979624
> -called for link 78268
> +cache hit 738093 = +432
> +cache miss 980524 = +900
> +called for link 78289 = +21
> multiple source files 373
> compile failed 5679
> preprocessor error 1594
> -not a C/C++ file 44512
> +not a C/C++ file 44549 = +37
>
> 1332 cacheable
> 58 uncacheable
>
>
> v2.6.28-7485-g9e42d0c:
>
> -cache hit 738096 = +9
> +cache hit 738105
> cache miss 980524 = +0
> -called for link 78293
> +called for link 79659 = +1366
> multiple source files 373
> compile failed 5679
> preprocessor error 1594
> -not a C/C++ file 44549 = +1384
> +not a C/C++ file 45933
>
> 9 cacheable
> 2750 uncacheable
>
>
> What changed?
Before we did a straight .c -> .o
Now we do .c -> .s -> .o to mark __crc_ symbols static so we can
kill them when stripping modules.
It is already being discussed in another thread.
See "[REGRESSION] Recent change to kernel spikes out ccache/distcc"
Sam
prev parent reply other threads:[~2009-01-08 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 4:03 Roland McGrath
2009-01-08 5:42 ` Sam Ravnborg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090108054215.GA11628@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®