From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/4] Big acceleration of Kbuild performance
Date: Thu, 27 Feb 2014 14:13:24 -0700 [thread overview]
Message-ID: <530FAA74.7010503@wwwdotorg.org> (raw)
In-Reply-To: <1393511304-9432-1-git-send-email-yamada.m@jp.panasonic.com>
On 02/27/2014 07:28 AM, Masahiro Yamada wrote:
> Kbuild brought about many advantages for us but
> a significant performance regression was reported by
> Simon Glass.
>
> After some discussions and analysis, it turned out
> its main cause is in $(call cc-option,...).
...
> Instead, you can also try my local branch for easy test.
>
> I pushed my local branch to my GitHub page.
> Please try the following.
>
> (1) git clone git://github.com/masahir0y/u-boot-kbuild.git
> (2) cd u-boot-kbuild
> (3) git checkout optimize_v1
I tried that since it was easier than applying all the patches. It built
and ran on real HW OK, although the U-Boot banner is a bit broken:
U-Boot SPL __DUMMY__ (DUMMY - DUMMY)
__DUMMY__ (DUMMY - DUMMY)
TEGRA20
Board: NVIDIA Seaboard
...
Hit any key to stop autoboot: 0
Tegra20 (SeaBoard) #
next prev parent reply other threads:[~2014-02-27 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 14:28 [U-Boot] [PATCH 0/4] Big acceleration of Kbuild performance Masahiro Yamada
2014-02-27 14:28 ` [U-Boot] [PATCH 1/4] kbuild, blackfin: Add CONFIG_CC_OPTIMIZE_LIBS_FOR_SPEED Masahiro Yamada
2014-02-27 14:28 ` [U-Boot] [PATCH 2/4] kbuild: add CONFIG_ prefix to USE_PRIVATE_LIBS Masahiro Yamada
2014-02-27 17:07 ` Stephen Warren
2014-02-28 4:50 ` Masahiro Yamada
2014-02-27 14:28 ` [U-Boot] [PATCH 3/4] config.mk: specify the exact path to standalone linker script Masahiro Yamada
2014-02-27 14:28 ` [U-Boot] [PATCH 4/4] kbuild: improve Kbuild speed Masahiro Yamada
2014-02-27 21:00 ` Simon Glass
2014-02-27 19:51 ` [U-Boot] [PATCH 0/4] Big acceleration of Kbuild performance Tom Rini
2014-02-27 21:13 ` Stephen Warren [this message]
2014-02-28 4:58 ` Masahiro Yamada
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=530FAA74.7010503@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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