public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: edk2-devel@lists.01.org
Cc: Yonghong Zhu <yonghong.zhu@intel.com>, Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH] BaseTools: improve C tools build time with GNU
Date: Tue, 5 Dec 2017 18:42:34 +0000	[thread overview]
Message-ID: <20171205184233.yarnpyfzdxjkalwh@bivouac.eciton.net> (raw)
In-Reply-To: <20171205180814.27267-1-leif.lindholm@linaro.org>

Hah, no ignore this.

I managed to not make it build the slow tools...

Back to the drawing board.

On Tue, Dec 05, 2017 at 06:08:14PM +0000, Leif Lindholm wrote:
> Commit 9e1131b70b4b
> ("BaseTools: Update BaseTools top GNUMakefile with the clear dependency")
> made parallel builds of BaseTools possible. However, the two utilities
> BrotliCompress and VfrCompile have substantially longer build (and
> especially link) time than the others - which leads to long waiting
> times. Build these two tools separately first, in order to reduce build
> time.
> 
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
> ---
> 
> For comparison, this reduces the build time on my x86 machine (8 cores,
> 16 threads) down from >9s to <3s.
> On the Cortex-A53 based 24-core SynQuacer platform, it takes the build
> time down from 1m26s to 20s.
> 
>  BaseTools/Source/C/GNUmakefile | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/BaseTools/Source/C/GNUmakefile b/BaseTools/Source/C/GNUmakefile
> index 0dc748267d..b7ddcb5022 100644
> --- a/BaseTools/Source/C/GNUmakefile
> +++ b/BaseTools/Source/C/GNUmakefile
> @@ -50,9 +50,11 @@ all: makerootdir subdirs
>  LIBRARIES = Common
>  VFRAUTOGEN = VfrCompile/VfrLexer.h
>  # NON_BUILDABLE_APPLICATIONS = GenBootSector BootSectImage
> -APPLICATIONS = \
> +SLOW_APPLICATIONS = \
>    BrotliCompress \
> -  VfrCompile \
> +  VfrCompile
> +
> +APPLICATIONS = \
>    GnuGenBootSector \
>    BootSectImage \
>    EfiLdrImage \
> @@ -72,7 +74,8 @@ APPLICATIONS = \
>  SUBDIRS := $(LIBRARIES) $(APPLICATIONS)
>  
>  $(LIBRARIES): $(MAKEROOT)/libs
> -$(APPLICATIONS): $(LIBRARIES) $(MAKEROOT)/bin $(VFRAUTOGEN)
> +$(SLOW_APPLICATIONS): $(LIBRARIES) $(MAKEROOT)/bin $(VFRAUTOGEN)
> +$(APPLICATIONS): $(SLOW_APPLICATIONS)
>  
>  .PHONY: outputdirs
>  makerootdir:
> -- 
> 2.11.0
> 


      reply	other threads:[~2017-12-05 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 18:08 [PATCH] BaseTools: improve C tools build time with GNU Leif Lindholm
2017-12-05 18:42 ` Leif Lindholm [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-list 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=20171205184233.yarnpyfzdxjkalwh@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /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