This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: same routines in multiple overlays
- From: Paul Koning <pkoning at equallogic dot com>
- To: oliver dot wohlmuth at freescale dot com
- Cc: binutils at sourceware dot org
- Date: Wed, 1 Feb 2006 09:50:05 -0500
- Subject: Re: same routines in multiple overlays
- References: <43E06BE3.4030709@freescale.com>
>>>>> "Oliver" == Oliver Wohlmuth <oliver.wohlmuth@freescale.com> writes:
Oliver> Hello, I'm using overlays to load time critical routines from
Oliver> external memory into on-chip memory. Depending on what
Oliver> "codec" is used, the appropriate overlay is loaded. This
Oliver> works fine so far.
Oliver> The problem is, that some routines are shared between
Oliver> different overlay (i.e. codecs). So far I defined a
Oliver> non-overlay area in on-chip memory to hold this common time
Oliver> critical routines. But not all common code is needed by all
Oliver> codecs; so I'm not utilizing the on-chip memory the most
Oliver> efficient way. Actually I'm running out of on-chip memory!
Oliver> Here comes my question: Is there a way in the linker script
Oliver> to tell ld (version 2.16.1) to move a static library into
Oliver> multiple overlays ? If not, does anybody know of other way to
Oliver> achieve this ?
I've never used overlays in ld, but I used them a lot back in the old
days of PDP-11s.
The most efficient answer is a tree structured overlay setup (as in
TKB, in RSX-11). The other answer that might work is multiple overlay
regions: one to hold semi-common pieces, the other to hold the
individual bits (as in RT-11). If you can do either of these,
preferably the former, you should be able to achieve what you need.
paul