Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!husc6!bloom-beacon!gatech!emory!platt
From: platt@emory.uucp (Dan Platt)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Microsoft C 4.0 large models
Message-ID: <2190@emory.uucp>
Date: Tue, 4-Aug-87 00:53:38 EDT
Article-I.D.: emory.2190
Posted: Tue Aug  4 00:53:38 1987
Date-Received: Thu, 6-Aug-87 01:34:03 EDT
References: <3225@cucca.columbia.edu> <3320039@hpsrlc.HP.COM>
Reply-To: platt@emory.UUCP (Dan Platt)
Distribution: world
Organization: Math & Computer Science, Emory University, Atlanta
Lines: 21
Keywords: huge pointers.
Summary: halloc();

In article <3320039@hpsrlc.HP.COM> darrylo@hpsrlc.HP.COM (Darryl Okahata) writes:
>In comp.sys.ibm.pc, nwc@cucca.columbia.edu (Nicholas W. Christopher) writes:
>
>> I wrote a language and interpreter using Lex, YACC and 
curses on a vax...
>> I tried compiling under a large model and the code ran for a while and then
>> froze. My question is, what are the things to worry about in large models?


There may also be problems with the amount of space required by a
malloc'ed data object (if you malloc something larger than 64k
the routine may lock up).  For this reason, huge structures and pointers are 
available, and halloc works like malloc to allocate memory but returns
huge model compatible pointers.

Also, you might want to check to see if you're running out of memory
(if your job calls in other process via 'system();' you may be
running into some problems (I've had problems with 'make' provided
with msc v4.00 if my segments are too large).

Dan