On Sat, 21 Aug 1999, Philip Blundell wrote:
> > I relise that but isn't this a common thing in RISC chips and
> >linkers/compilers use long jump?
>
> What do you mean by "long jump"?
Isn't long jump a gcc function used to make cals to functions
further away then the branch inst allows? I might be confusing it
something else though.
>
> >> (Why do you want to do this in the first place, by the way?)
> >>
> > I have initialiseation an initialisation section and a kernel text
> >section (both loadable segments) The initialisation section is mapped
> >one-one at 0xC0100000 (on the SA-1100) and the text section is mapped to
> >0xFFFF0000. I have debugging calls in the text section that I try to call
> >from the init sectin (putc, printf, dumpPT, etc) but the 26bit branching
> >gets in the way. I could use ASM macro's to make the calls but this seems
> >abit messy, is there a nice solution to this problem. Another solution is
> >to have the functions linked in both sections with different names but
> >again I think this is a bit messy.
>
> Well, -fPIC is the obvious solution if you can handle the overhead.
Ah cheers, such a simple solution. Since its initialisation and
debugging code only that will be compiled like this its fine.
Many thanks, Adam
>
> p.
>
>
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
