From: Daniel Schwierzeck <daniel.schwierzeck@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] config.mk: use memoization in cc-option macro to speed up compilation
Date: Wed, 02 Nov 2011 22:36:29 +0100 [thread overview]
Message-ID: <4EB1B7DD.40704@googlemail.com> (raw)
In-Reply-To: <CAPnjgZ3VtmRH9bFhOonJsVipkRsoXBnnoatUtn4gjju1zbr7JQ@mail.gmail.com>
Hi Simon,
On 02.11.2011 21:39, Simon Glass wrote:
...
>>
>> diff --git a/config.mk b/config.mk
>> index 11b67e5..27c366f 100644
>> --- a/config.mk
>> +++ b/config.mk
>> @@ -107,8 +107,22 @@ HOSTCFLAGS += -pedantic
>> # Option checker (courtesy linux kernel) to ensure
>> # only supported compiler options are used
>> #
>> +ifeq ($(CACHE_CC_OPTIONS),y)
>> +sinclude $(OBJTREE)/include/cc-options.mk
>
> It would be better to put this into include/generated - it will also
> make git ignore it and it will be also be removed on clobber which I
> think you need.
The patch is still experimental. But I will move that file to
include/generated in the final version.
>
>> +
>> +cc-option-cached = $(shell if $(CC) $(CFLAGS) $(1) -S -o /dev/null -xc /dev/null \
>> +> /dev/null 2>&1; then \
>> + echo 'CC_OPTIONS += $(strip $1)' \
>> +>> $(OBJTREE)/include/cc-options.mk; \
>> + echo "$(1)"; else echo "$(2)"; fi ;)
>> +
>> +cc-option = $(if $(filter $1,$(CC_OPTIONS)),\
>> + $(filter $1,$(CC_OPTIONS)),\
>> + $(call cc-option-cached,$1,$2))
>> +else
>> cc-option = $(shell if $(CC) $(CFLAGS) $(1) -S -o /dev/null -xc /dev/null \
>> > /dev/null 2>&1; then echo "$(1)"; else echo "$(2)"; fi ;)
>> +endif
>>
>
> Tested-by: Simon Glass<sjg@chromium.org>
>
> With this patch and Wolfgang's I get 1.122s for an incremental build
> now. Now I just need faster SPI flash and a faster car to get to work
> sooner.
>
> Is there any reason not to enable this option by default?
To see the difference between compilation times with and without this
optimization and to do not break existing code. In the final version I
would remove the config switch and enable the optimization by default ;)
Best regards,
Daniel
next prev parent reply other threads:[~2011-11-02 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 18:46 [U-Boot] [PATCH] config.mk: use memoization in cc-option macro to speed up compilation Daniel Schwierzeck
2011-11-02 20:39 ` Simon Glass
2011-11-02 21:36 ` Daniel Schwierzeck [this message]
2011-11-03 19:47 ` Wolfgang Denk
2011-11-04 12:53 ` [U-Boot] [PATCH v2] " Daniel Schwierzeck
2011-11-04 16:32 ` Simon Glass
2011-11-04 17:15 ` Daniel Schwierzeck
2011-11-04 17:31 ` Daniel Schwierzeck
2011-11-04 17:56 ` Wolfgang Denk
2011-11-05 9:16 ` Albert ARIBAUD
2011-11-05 13:30 ` Wolfgang Denk
2011-11-05 13:43 ` Daniel Schwierzeck
2011-11-05 15:02 ` Albert ARIBAUD
2011-11-07 15:26 ` [U-Boot] [PATCH v3] " Daniel Schwierzeck
2011-11-07 21:07 ` Wolfgang Denk
[not found] ` <1320410756-30391-1-git-send-email-daniel.schwierzeck@googlemail.com>
2011-11-05 7:17 ` [U-Boot] [PATCH v2] " Aneesh V
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=4EB1B7DD.40704@googlemail.com \
--to=daniel.schwierzeck@googlemail.com \
--cc=u-boot@lists.denx.de \
/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