From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] patch for gc-sections
Date: Thu, 04 Nov 2010 11:36:11 -0500 [thread overview]
Message-ID: <1288888571.8967.1598.camel@petert> (raw)
In-Reply-To: <1288887364.1796.237.camel@haiying-laptop>
> Yes, you are right, the size is down. I only noticed the u-boot-spl size
> by using ls -l, not via size. Now I get the same result as yours.
>
> It is very good to see this trim-down size because I know some board
> developers are fighting with the 4k limitation of the nand-spl size. Are
> you going to submit your new patch to upstream?
Glad to hear. I'll submit an official patch shortly. Just to make
sure, have you tried running one of the nand-spl images after the patch
I sent yesterday? It'd be good to get confirmation that the
-gc-sections doesn't have any accidental side effects as I wasn't able
to test it.
> Btw, the filesize I see here is smaller than yours, I guess you are
> using the most updated gcc version. I am using gcc-4.3.2.
I was using gcc 4.2.2 in my tests for what its worth.
> > I batted an eye when I saw the 112M file to, but it looks like that is
> > unrelated to my change:
> It is not related to your change, I see it happens on 2010.09 which
> doesn't have your change. Something between 2010.06 and 2010.09 makes
> this happen.
One more bug to track down:)
Best,
Peter
next prev parent reply other threads:[~2010-11-04 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 19:07 [U-Boot] patch for gc-sections Haiying Wang
2010-11-03 20:38 ` Peter Tyser
2010-11-04 14:19 ` Haiying Wang
2010-11-04 15:45 ` Peter Tyser
2010-11-04 16:16 ` Haiying Wang
2010-11-04 16:36 ` Peter Tyser [this message]
2010-11-04 18:22 ` Haiying Wang
2010-11-10 19:25 ` Haiying Wang
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=1288888571.8967.1598.camel@petert \
--to=ptyser@xes-inc.com \
--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