From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Observation: rebasing against current master increases code size by 1.8k
Date: Wed, 20 Oct 2010 04:11:52 -0400 [thread overview]
Message-ID: <201010200411.53387.vapier@gentoo.org> (raw)
In-Reply-To: <4CBEA212.6030502@emk-elektronik.de>
On Wednesday, October 20, 2010 04:02:26 Reinhard Meyer wrote:
> Mike Frysinger wrote:
> > On Wednesday, October 20, 2010 03:30:33 Reinhard Meyer wrote:
> >> Just an observation on my AT91SAM9XE based board:
> >>
> >> based on yesterday's master + arm elf relocations +
> >> my (then not mainstreamed) patches: 256288 bytes
> >>
> >> based on current master: 258020 bytes
> >>
> >> Otherwise it compiles without warnings and runs fine.
> >> Just some non-reloc-related patches have increased
> >> code size by that amount - finding out which are to
> >> "blame" is probably not worth the effort.
> >
> > look at the env change ?
> >
> > ea882baf9c17cd142c99e3ff640d3ab01daa5cec
>
> That (old) commit was in mainstream already. Related fixups
> do not matter for my board since env_mmc ist not included
> and ARM_RELOC_FIXUP_WORKS is set.
it isnt old. it was *committed* a while ago, but wasnt *merged* into mainline
until after the latest release (v2010.09). so it's new to the master branch.
that's the only common code change that pops into my mind after the v2010.09
release was made.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20101020/64149e48/attachment.pgp
prev parent reply other threads:[~2010-10-20 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 7:30 [U-Boot] Observation: rebasing against current master increases code size by 1.8k Reinhard Meyer
2010-10-20 7:42 ` Mike Frysinger
2010-10-20 8:02 ` Reinhard Meyer
2010-10-20 8:11 ` Mike Frysinger [this message]
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=201010200411.53387.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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