Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!decvax!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Request for Compiler Info
Message-ID: <8710262044.AA08743@cory.Berkeley.EDU>
Date: Mon, 26-Oct-87 15:44:47 EST
Article-I.D.: cory.8710262044.AA08743
Posted: Mon Oct 26 15:44:47 1987
Date-Received: Wed, 28-Oct-87 07:36:24 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 20

>Manx uses a bogus "memory model" scheme to avoid having to do a good
>optimisation job. But even in their large model they're faster than Lattice.
>I always use large model myself... if I wanted a segmented architecture
>I would have gone with IBM. No smiley.

	Not at all... you can think of it as:

	small/large data:	do I want to use relative or absolute addresses
	small/large code:	do I want to use pc-rel or absolute addresses

	relative addressing takes one word less than absolute addressing, thus
	causing a not-so-trivial speedup when accessing global/static 
	variables.  Referencing auto (stack) variables doesn't change since
	they are SP-relative anyway.  

	So for something like ... my TEST: device, there is no difference 
	since I have few global variables.  Something like DME or SHELL,
	however, have *lots* of global variables.

					-Matt