Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!ptsfa!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!aglew
From: aglew@ccvaxa.UUCP
Newsgroups: comp.arch
Subject: Re: Big Programs Hurt Performance
Message-ID: <28200049@ccvaxa>
Date: Thu, 24-Sep-87 10:23:00 EDT
Article-I.D.: ccvaxa.28200049
Posted: Thu Sep 24 10:23:00 1987
Date-Received: Sun, 27-Sep-87 02:52:44 EDT
References: <417@devvax.JPL.NASA.GOV>
Lines: 16
Nf-ID: #R:devvax.JPL.NASA.GOV:417:ccvaxa:28200049:000:636
Nf-From: ccvaxa.UUCP!aglew    Sep 24 09:23:00 1987


...> Position Independent Code

Note that PC relative addressing is not a strict requirement
for Position Independent Code.

Many fast machines cannot generate PCs quickly enough to be used in
addressing without a delay - that is, they cannot generate a PC
accurate to byte, word, or doubleword quiickly enough, and the rules
for the inaccuracy are probabilistic.
	However, they may be able to generate, say, the page number
that the PC is in.

With this type of addressing you get Position Independent Code to
a certain granularity - ie. you can vary addresses by a multiple of
pages, but not within a page. Often this is good enough.