On Mon, Apr 12, 2010 at 23:25, Gavin Lambert <gav...@compacsort.com> wrote:
> Quoth Geert Uytterhoeven:
>> b. Use 2 separate stacks:
>> 1. The standard stack for return addresses (jump to
>> subroutine), so you can relocate all addresses (pointers
>> to code) when moving/copying the code,
>> 2. A second stack for storing data (mix of "pointers"
>> and other variables), which you don't touch when moving
>> (remember, all pointers are actually offsets relative to
>> the base register).
>
> What about other pointers to code (vtables, app-defined variables, etc)? I
> don't think you can rely on everything being in the stack.
PC-relative adressing?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
