From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Guillaume Tucker <guillaume.tucker@collabora.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH] arm64: defconfig: Disable DEBUG_INFO
Date: Thu, 4 Mar 2021 16:35:06 +0000 [thread overview]
Message-ID: <20210304163506.GD4731@sirena.org.uk> (raw)
In-Reply-To: <20210304162231.GA29547@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
On Thu, Mar 04, 2021 at 04:22:32PM +0000, Catalin Marinas wrote:
> How about enabling DEBUG_INFO_REDUCED as a middle ground? For me the
> build tree goes from 5.9GB to 2.0GB. I tried faddr2line and still works
> as expected (only tried gcc, not sure whether clang honours this
> option).
That seems like a good tradeoff for me - it's only 100% bigger than no
debug info at all.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-04 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 18:58 [PATCH] arm64: defconfig: Disable DEBUG_INFO Mark Brown
2021-03-03 19:24 ` Kevin Hilman
2021-03-04 12:56 ` Will Deacon
2021-03-04 14:36 ` Mark Brown
2021-03-04 14:48 ` Will Deacon
2021-03-04 15:18 ` Mark Brown
2021-03-04 16:22 ` Catalin Marinas
2021-03-04 16:35 ` Mark Brown [this message]
2021-03-04 17:24 ` Kevin Hilman
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=20210304163506.GD4731@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=guillaume.tucker@collabora.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).