Xref: utzoo comp.lang.c:35850 comp.os.msdos.programmer:3179 comp.os.os2.misc:655 comp.os.os2.programmer:431
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!ubc-cs!unixg.ubc.ca!cheddar.ucs.ubc.ca!ballard
From: ballard@cheddar.ucs.ubc.ca (Alan Ballard)
Newsgroups: comp.lang.c,comp.os.msdos.programmer,comp.os.os2.misc,comp.os.os2.programmer
Subject: Re: Copiling warning, C4058 of MSC V5.1 - DS != SS
Message-ID: <1991Feb6.180813.12005@unixg.ubc.ca>
Date: 6 Feb 91 18:08:13 GMT
References: <1991Feb6.091030.27891@hellgate.utah.edu>
Sender: news@unixg.ubc.ca (Usenet News Maintenance)
Organization: Computing Services, University of British Columbia
Lines: 21

In article <1991Feb6.091030.27891@hellgate.utah.edu> h-lee%hogum.utah.edu@cs.utah.edu (LEE Hyo Jong) writes:
>I got the warning of 'address of frame variable taken, DS!=SS'.
>It usually happens when I calls the math lib functions such as
>pow() or sin() or when I manipulate three dimensional arrays.
>Since I am using multithread, one of my compile options(MSC V5.1) is
>-Aluf.
 
Hm, this should only happen if you're passing a near pointer, which
shouldn't occur with -Aluf.  Is it possible the functions involved
have explicit "near" attributes for parameters etc.?   
 
I have managed to suppress this message in the past, in situations where
SS was == DS, even though the compiler didn't know it, by using casts. 
Don't remember the details: something like a cast to a far pointer then
a cast to a near pointer. 


Alan Ballard                   | Internet: ballard@ucs.ubc.ca
University Computing Services  |   Bitnet: USERAB1@UBCMTSG
University of British Columbia |    Phone: 604-228-3074
Vancouver B.C. Canada V6R 1W5  |      Fax: 604-228-5116