Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mcdchg!behemoth!mph
From: mph@behemoth.phx.mcd.mot.com (Mark Huth)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Address Spaces (was Re: (Fairly) Complete Amiga VM design)
Keywords: virtual memory, address space
Message-ID: <11097@behemoth.phx.mcd.mot.com>
Date: 15 Jun 89 19:24:11 GMT
References: <8906010252.AA11810@jade.berkeley.edu> <367@xdos.UUCP> <54912@linus.UUCP> <377@xdos.UUCP> <55595@linus.UUCP>
Reply-To: mph@behemoth.UUCP (Mark Huth)
Organization: Motorola Microcomputer Division, Tempe, Az.
Lines: 19

In article <55595@linus.UUCP> eachus@mbunix.mitre.org (Robert I. Eachus) writes:
>specific locations in memory.  However, beginning with the PDP-11, a
>technique called position independant code was available which
>permitted code to be loaded without relocation.  The VAX and 68000
>
>     The Amiga from day one has required that code be written this
>way, and on the 68000 family this type of code is generally faster.

Sorry, the Amiga relocates stuff at load time - thats what the REL32 hunk types 
are for.  The object code I've looked at on the Amiga is a curious mixture of
PIC and bound code, with base register addressing thrown in for library
references.

The Amiga allows just about any type of code to be written and loaded, just as
the 68000 support most addressing modes - and by the time you get to the '020+
you finally get full support for PIC.  The 68000 PC relative addressing is
limited to +/- 32k bytes.

Mark Huth