All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH v3 2/2] ci: Add a test for a non-LTO build
Date: Sun, 7 Aug 2022 09:48:01 -0600	[thread overview]
Message-ID: <CAPnjgZ1SLFjGfb=+CnLv18UqujbC20Mqm+TTxgw0QcqSX4J=ng@mail.gmail.com> (raw)
In-Reply-To: <20220803121301.v3.2.Ib592f574bd629316a4da239b054fdad8af2658a3@changeid>

Hi Tom,

On Wed, 3 Aug 2022 at 12:13, Simon Glass <sjg@chromium.org> wrote:
>
> Check that sandbox builds and runs tests OK with LTO disabled.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> (no changes since v1)
>
>  .azure-pipelines.yml | 4 ++++
>  .gitlab-ci.yml       | 7 +++++++
>  2 files changed, 11 insertions(+)
>

Another little snippet - it seems that CI performance for the world
builds has dropped 20% - 30% with LTO enabled. With tui I used to see
just over 1 build a second; now it is running at about 0.78 and kaki
has gone from close to 0.5 to 0.29.

I wonder if ,in CI, we should just build a selection of boards with
LTO, switching the world builds to non-LTO? The problem is that we may
hit code size limits in SPL.

Regards,
Simon

  reply	other threads:[~2022-08-07 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 18:13 [PATCH v3 1/2] Makefile: Allow LTO to be disabled for a build Simon Glass
2022-08-03 18:13 ` [PATCH v3 2/2] ci: Add a test for a non-LTO build Simon Glass
2022-08-07 15:48   ` Simon Glass [this message]
2022-08-08 16:09     ` Tom Rini
2022-08-09 19:51       ` Simon Glass
2022-08-09 20:10         ` Tom Rini
2022-09-03  1:54   ` Tom Rini
2022-09-01  2:26 ` [PATCH v3 1/2] Makefile: Allow LTO to be disabled for a build Simon Glass
2022-09-03  1:54 ` Tom Rini

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='CAPnjgZ1SLFjGfb=+CnLv18UqujbC20Mqm+TTxgw0QcqSX4J=ng@mail.gmail.com' \
    --to=sjg@chromium.org \
    --cc=bmeng.cn@gmail.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.