[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <40412179-9bc2-409b-ab12-11149a3e4f5f@app.fastmail.com>
Date: Sat, 07 Sep 2024 12:03:48 +0000
From: "Arnd Bergmann" <arnd@...db.de>
To: "Florian Fainelli" <florian.fainelli@...adcom.com>,
linux-arm-kernel@...ts.infradead.org
Cc: "Russell King" <linux@...linux.org.uk>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>,
"Marek Szyprowski" <m.szyprowski@...sung.com>,
"Geert Uytterhoeven" <geert+renesas@...der.be>, "Andrew Davis" <afd@...com>,
"Jason Gunthorpe" <jgg@...pe.ca>, "Mark Brown" <broonie@...nel.org>,
"Etienne Carriere" <etienne.carriere@...s.st.com>,
"Trevor Woerner" <twoerner@...il.com>,
"Javier Carrasco" <javier.carrasco@...fvision.net>,
"open list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Enable debugging symbols by default
On Fri, Sep 6, 2024, at 21:39, Florian Fainelli wrote:
> Similarly to the ARM64 defconfig, enable debugging symbols and rely upon
> the toolchain's default DWARF implementation.
>
> Signed-off-by: Florian Fainelli <florian.fainelli@...adcom.com>
I usually build with debug info disabled when I'm build testing,
but turn it on explicitly when I try to actually debug a problem.
Depending on the configuration, adding debug info can significantly
increase the build time and file size. I've tried to record exact
data here, building the arm defconfig on gcc-14 with and without
debug info, which doesn't seem too bad, especially with the
reduced debug info:
config vmlinux time total time vmlinux size
disabled-gcc9 49s 81s 35MB
reduced-gcc9 55s 98s 148MB
full-gcc9 66s 105s 443MB
disabled-gcc14 55s 90s 34MB
reduced-gcc14 60s 99s 124MB
full-gcc14 68s 115s 349MB
There is still added disk usage for build testing, but
the time overhead seems fine. I'd like to hear what others
think about the tradeoff.
Arnd
Powered by blists - more mailing lists