Caution for those considering MSC 5.0

[Jerry Fountain]

In article <UW2DrLy00VsGZ8I0CK at andrew.cmu.edu> mc35+ at andrew.cmu.edu (Mark Chance) writes:
>In recompiling my application under 5.0 I discovered an annoying
>feature which effectively prevents me from using 5.0.  My application is
>pretty large and I need a lot of stack space.  I am using the large
>model and by adding the -Gt option to force data items to their own
>segment things are pretty cool.  Now along comes 5.0 and I specify 20000
>bytes stack space, the linker says 'Error: stack+data>64K'.  I say how
>can that be?  Well the punch line is that 5.0 puts strings in the
>CONST space which is in the stack segment !!! :-(.  So cluttering up my
>precious stack space is 40K worth of strings that used to be distributed
>among the various FAR-DATA segments.  I intend to complain to Microsoft
>about this since I have not found any compiler switches to avoid this.
>Any other ideas?
>
>Mark Chance                Information Technology Center
>mc35+ at andrew.cmu.edu       Carnegie-Mellon Univ.


I think you should have contacted MS before putting out this minor flame
(or at least have posted it as a question to the net rather than a complaint)

What you need to do is call MS, and tell them you need the 'Gt fix for the
second pass of the compiler.'  This makes 5.0 work like 4.0 (makes CONST
-Gt aware).  They will send you a replacement second pass for the compiler.
Note:  When I spoke with them about the 'bug' they stated they did not
consider it a bug but simply a design change.  In reality it only effects 
those with a large stack requirement or a large number of CONST's


-- 
-----Jerry Fountain-----
UUCP: {hplabs!hp-sdd,sdcsvax,nosc}!crash!pnet01!gof   ARPA: crash!gof at nosc.mil
MAIL: 523 Glen Oaks Dr., Alpine, Calif. 92001         INET: gof at pnet01.CTS.COM