Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!cs.umn.edu!quest!orbit!pnet51!chucks
From: chucks@pnet51.orb.mn.org (Erik Funkenbusch)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: > SAS gripes (was DICE vs GCC)
Message-ID: <4573@orbit.cts.com>
Date: 11 Apr 91 17:25:01 GMT
Sender: news@orbit.cts.com
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 19

lofaso@triumph.tsd.arlut.utexas.edu (Bernie Lofaso) writes:
>In article <1991Apr5.173845.4404@nntp-server.caltech.edu>, tll@nntp-server.caltech.edu (Tal Lewis Lancaster) writes:
>
>> Well the main reason is I am creating object files greater than 32K (actually
>> some are around 80K).  SAS and Aztec can not handle object files > 32K.  Or to
>> be more precise a function call to another function in the same object file must
>> be < 32K apart.
>
>Sorry, but this is not true. The 32K limit is only for a small code model.
>You can specify a large memory model for code with a compiler switch and
>the object modules can be any size you want. This pertains to Aztec C but I
>would expect SAS to have similar functionality.


And actually, even in small code and data it can still be >32k.  if it is,
though  it will incurr a loss of performance do to the jump table lookups.
UUCP: {amdahl!tcnet, crash}!orbit!pnet51!chucks
ARPA: crash!orbit!pnet51!chucks@nosc.mil
INET: chucks@pnet51.orb.mn.org