From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] cc1 and cc1plus had about 20 mbytes of debug information each, in the final redistributable form. This patch strips those two binaries yielding a savings of about 40 mbytes per SDK.
Date: Mon, 7 Mar 2011 12:08:10 -0700 [thread overview]
Message-ID: <4D752D1A.6050808@mentor.com> (raw)
In-Reply-To: <1299522811-2065-1-git-send-email-dick@softplc.com>
On 03/07/2011 11:33 AM, Dick Hollenbeck wrote:
> Signed-off-by: Dick Hollenbeck<dick@softplc.com>
We recently added logic to conf/distro/include/sane-toolchain-* to
handle the debug level via DEBUG_LEVEL. Would you mind adding a
DEBUG_LEVEL_HOST to conf/bitbake.conf and making BUILD_OPTIMIZATION obey
that instead so that we can drop debug info from all of them? Thanks.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-07 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 18:33 [PATCH] cc1 and cc1plus had about 20 mbytes of debug information each, in the final redistributable form. This patch strips those two binaries yielding a savings of about 40 mbytes per SDK Dick Hollenbeck
2011-03-07 19:08 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 19:57 Dick Hollenbeck
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=4D752D1A.6050808@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.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 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.