From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Andre Przywara <andre.przywara@arm.com>,
Artem Lapkin <email2tema@gmail.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Icenowy Zheng <icenowy@aosc.io>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Peng Fan <peng.fan@nxp.com>, Samuel Holland <samuel@sholland.org>,
Ye Li <ye.li@nxp.com>
Subject: Re: [PATCH v3 1/2] Makefile: Allow LTO to be disabled for a build
Date: Fri, 2 Sep 2022 21:54:26 -0400 [thread overview]
Message-ID: <20220903015426.GK7942@bill-the-cat> (raw)
In-Reply-To: <20220803181309.29999-1-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
On Wed, Aug 03, 2022 at 12:13:08PM -0600, Simon Glass wrote:
> LTO (Link-Time Optimisation) is an very useful feature which can
> significantly reduce the size of U-Boot binaries. So far it has been
> made available for selected ARM boards and sandbox.
>
> However, incremental builds are much slower when LTO is used. For example,
> an incremental build of sandbox takes 2.1 seconds on my machine, but 6.7
> seconds with LTO enabled.
>
> Add a NO_LTO parameter to the build, similar to NO_SDL, so it can be
> disabled during development if needed, for faster builds.
>
> Add some documentation about LTO while we are here.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-09-03 1:54 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
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 [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=20220903015426.GK7942@bill-the-cat \
--to=trini@konsulko.com \
--cc=andre.przywara@arm.com \
--cc=email2tema@gmail.com \
--cc=icenowy@aosc.io \
--cc=ilias.apalodimas@linaro.org \
--cc=peng.fan@nxp.com \
--cc=samuel@sholland.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yamada.masahiro@socionext.com \
--cc=ye.li@nxp.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 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.