Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!gt-eedsp!emory!platt
From: platt@emory.UUCP (Dan Platt)
Newsgroups: comp.lang.c,comp.sys.ibm.pc,comp.sys.intel
Subject: Re: C compilers that can access more memory
Message-ID: <2091@emory.UUCP>
Date: Tue, 16-Jun-87 00:20:00 EDT
Article-I.D.: emory.2091
Posted: Tue Jun 16 00:20:00 1987
Date-Received: Sun, 21-Jun-87 06:37:08 EDT
References: <496@tahoe.UUCP>
Reply-To: platt@emory.UUCP (Dan Platt)
Organization: Math & Computer Science, Emory University, Atlanta
Lines: 19
Keywords: More C Memory
Xref: mnetor comp.lang.c:2530 comp.sys.ibm.pc:4908 comp.sys.intel:270

In article <496@tahoe.UUCP> malc@tahoe.UUCP (Malcolm L. Carlock) writes:
>I'm looking for a C compiler to run on '286 AT's or AT clones that can
>access more than 64K of program and 64K of data memory.  Microsoft C and
>MIX C both seem to be unable to access more than 64K of either. 
>these machines using C.
>...
>Anyone out there have any ideas?

MS C ver 4.0 can access over 64k in code, and data structures larger than
64k.  By judicious use of pointers and malloc(), many structures in excess of
64k may be written in ver3.0.  The code segments may not exceed 64k; this 
meaning that the compiled code for any one compiled segment may not exceed
64k, but lots of these may be linked together to produce code in excess of
64k.  (This is also true of their Pascal, which has extended memory allocation
routines like malloc()).  So, at least for Microsoft C, there should be no
real problem as far as running into code or memory problems (your memory
is the limit).

Dan