[U-Boot] Relocation size penalty calculation

Mike Frysinger
2009-10-09T01:25:47Z

On Thursday 08 October 2009 18:20:18 Peter Tyser wrote:
> On Fri, 2009-10-09 at 09:02 +1100, Graeme Russ wrote:
> > On Fri, Oct 9, 2009 at 8:23 AM, Wolfgang Denk <wd@denx.de> wrote:
> > > Graeme Russ wrote:
> > >> Once the reloc branch has been merged, how many arches are left which
> > >> do not support relocation?
> > >
> > > All but PPC ?
> >
> > Hmm, so commit 0630535e2d062dd73c1ceca5c6125c86d1127a49 is all about
> > removing code that is not used because these arches do not do any
> > relocation at all?
>
> I sent that patch/RFC after noticing none of those architectures
> performed manual relocation fixups, thus they could save some code space
> by defining CONFIG_RELOC_FIXUP_WORKS. Similarly the gd->reloc_off field
> was no longer needed for them.
>
> I'm not familiar with if or how those architectures are relocating, just
> that they didn't need relocation fixups. So that was the logic...

the usage in the Blackfin port is most likely a copy & paste of existing code.
deleting malloc_bin_reloc() from lib_blackfin/board.c and adding
CONFIG_RELOC_FIXUP_WORKS results in a working boot. ive never really looked
into relocation as no one has asked for it.
-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/20091008/d42e7117/attachment.pgp