public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
	Marek Vasut <marex@denx.de>, Stefano Babic <sbabic@denx.de>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: Thoughts about U-boot binary size increase
Date: Thu, 28 Mar 2024 08:18:32 -0400	[thread overview]
Message-ID: <20240328121832.GL3442575@bill-the-cat> (raw)
In-Reply-To: <20240328102049.10108d5b@wsk>

[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]

On Thu, Mar 28, 2024 at 10:20:49AM +0100, Lukasz Majewski wrote:
> Dear Community,
> 
> I'd like to share with you some thoughts about growth of u-boot's
> binary size for SPL and u-boot proper.
> 
> Board: XEA
> SoC  : imx287 (still in active production)
> Problem: SPL size constrained to ~55 KiB (This cannot be exceeded). 
> 	 Board design constraints u-boot proper size to less than ~448
> 	 KiB
> 
> 
> When XEA was added (2019.07):
> 	- u-boot.sb (SPL): 37 KiB
> 	- u-boot.img 	 : 401 KiB
> 
> Now (2024.04):
> 	- u-boot.sb (SPL): 40 KiB
> 	- u-boot.img 	 : 427 KiB
> 
> (With a _lot_ of effort put to reduce the size)
> 
> Hence, the question - would it be possible to take more concern about
> the binary size growth?
> 
> Maybe CI could catch patches, which enable by default some features and
> the size is unintentionally increased?
> 
> I'm open for any feedback and thoughts on "stopping" the binary size
> increase.

I think that's pretty amazingly small growth for nearly 5 years of bug
fixes and feature enhancements that it's likely minor to make granular.
If LTO is not enabled on this platform you should be able to use
buildman to give you a "bloat" list from v2019.07 to v2024.04 and see if
anything sticks out as being something that can be addressed. But that
little growth seems pretty good to me at first glance.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2024-03-28 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28  9:20 Thoughts about U-boot binary size increase Lukasz Majewski
2024-03-28  9:40 ` Marek Vasut
2024-03-28 10:29   ` Lukasz Majewski
2024-03-28 12:18 ` Tom Rini [this message]
2024-03-28 12:55   ` Lukasz Majewski
2024-03-28 12:58     ` Tom Rini
2024-03-28 13:03       ` Lukasz Majewski
2024-03-28 12:18 ` Fabio Estevam
2024-03-28 12:52   ` Lukasz Majewski

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=20240328121832.GL3442575@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=festevam@gmail.com \
    --cc=lukma@denx.de \
    --cc=marex@denx.de \
    --cc=sbabic@denx.de \
    --cc=sjg@chromium.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