Skip to contentSkip to conversation

Observation: rebasing against current master increases code size by 1.8k

U-Boot Reinhard Meyer 2 participants 4 messages Oct 20, 2010

lore
Share & tools
lore
#0 lore raw

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.

Best Regards,
Reinhard

#1 lore raw
Quoted 11 lines · 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

-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/a815d9c7/attachment.pgp

#2 lore raw

Dear Mike Frysinger,

Quoted 8 lines · On Wednesday, October 20, 2010 03:30:33 Reinhard Meyer wrote:
Quoted 7 lines

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

Quoted 7 lines
Quoted 4 lines

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.

Reinhard

#3 lore raw
Quoted 14 lines · On Wednesday, October 20, 2010 04:02:26 Reinhard Meyer wrote:
Quoted 13 lines · Mike Frysinger
Quoted 11 lines · 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.

Quoted 7 lines
Quoted 3 lines

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