Path: utzoo!attcan!uunet!husc6!rutgers!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!Ralf.Brown@B.GP.CS.CMU.EDU
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.sys.ibm.pc
Subject: Re: MIX Power C compiler (memory model names)
Message-ID: <22fc46fd@ralf>
Date: 7 Aug 88 13:03:09 GMT
Sender: netnews@pt.cs.cmu.edu
Lines: 20
In-Reply-To: <3018@ttidca.TTI.COM>

In article <3018@ttidca.TTI.COM>, svirsky@ttidca.TTI.COM (William Svirsky) writes:
}The compiler supports only what MIX calls an "enhanced medium model". 
}What this means is that they take the standard medium model (unlimited
}code/64K data) and add an unlimited size heap.  I haven't had a chance
}to play with this aspect of the compiler at all.

Sounds like what TurboC and probably everybody else calls "large model".  The
large model uses unlimited code/64K global data/unlimited heap (all pointers
are 32-bits, but global data is accessed relative to DS for faster/smaller
code).  "Huge model" uses one 64K global data segment per source file, but
this imposes extra overhead in loading DS on EVERY function entry.

If MIX really has added an unlimited heap to the standard medium model, how
can the compiler tell whether to use 16-bit pointers (for the 64K data
segment) or 32-bit pointers (for the heap)?
--
UUCP: {ucbvax,harvard}!cs.cmu.edu!ralf -=-=-=- Voice: (412) 268-3053 (school)
ARPA: ralf@cs.cmu.edu  BIT: ralf%cs.cmu.edu@CMUCCVMA  FIDO: Ralf Brown 1:129/31
Disclaimer? I     |Ducharm's Axiom:  If you view your problem closely enough
claimed something?|   you will recognize yourself as part of the problem.