From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eugeniu Rosca Date: Wed, 22 May 2019 16:15:47 +0200 Subject: [U-Boot] Making U-Boot smaller In-Reply-To: <8fccaded-bf4c-63d1-2241-059c091f28cd@denx.de> References: <1b28727d-efb0-cadb-4541-9383d4056808@denx.de> <20190521195311.GP22232@bill-the-cat> <21ce98e8-d687-14dc-5023-d7e005cf5c74@denx.de> <20190521195915.GQ22232@bill-the-cat> <2989d436-5cbd-5b1a-9bdd-14b7b0770e4a@denx.de> <20190521201003.GR22232@bill-the-cat> <8fccaded-bf4c-63d1-2241-059c091f28cd@denx.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de cc: Yamada-san I dream of a (Kconfig/Kbuild-assisted) bloaty-like output [1] which would point out the culprit configs. This is hardly achievable, but looks good on the paper! CONFIG FILE SIZE ------------ -------------- CONFIG_FEATURE_A 10.7Mi 37.1% CONFIG_FEATURE_B 5.39Mi 18.6% CONFIG_FEATURE_C 4.48Mi 15.5% CONFIG_FEATURE_D 1.86Mi 6.4% CONFIG_FEATURE_E 1.67Mi 5.8% CONFIG_FEATURE_F 1.61Mi 5.6% CONFIG_FEATURE_G 856Ki 2.9% CONFIG_FEATURE_H 470Ki 1.6% .... TOTAL 28.9Mi 100.0% [1] https://github.com/google/bloaty -- Best regards, Eugeniu