Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!bridge2!jarthur!nntp-server.caltech.edu!tll
From: tll@nntp-server.caltech.edu (Tal Lewis Lancaster)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: > SAS gripes (was DICE vs GCC)
Message-ID: <1991Apr9.160335.15914@nntp-server.caltech.edu>
Date: 9 Apr 91 16:03:35 GMT
References: <9104021420.AA10848@thunder.LakeheadU.Ca> <1991Apr5.173845.4404@nntp-server.caltech.edu> <24@triumph.tsd.arlut.utexas.edu>
Organization: California Institute of Technology, Pasadena
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.

Sorry, this is true.  I have confirmed it with SAS and Aztec!  It doesn't
matter which memory model you pick.  They both have <32K function call
limitation to calls in the same object file.

Tal Lancaster