Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!alberta!ubc-cs!uw-beaver!cornell!rochester!bbn!uwmcsd1!ig!agate!ucbvax!decwrl!spar!snjsn1!aconcagua!
From: bob@aconcagua (Bob Firestine)
Newsgroups: comp.os.vms
Subject: Re: VMS C version 2.3 optimize bug?
Message-ID: <277@snjsn1.SJ.ATE.SLB.COM>
Date: 2 Jun 88 20:05:17 GMT
Article-I.D.: snjsn1.277
References: <2099@ucdavis.ucdavis.edu> <2101@ucdavis.ucdavis.edu>
Sender: news@SJ.ATE.SLB.COM
Reply-To: bob%sjsca4@spar.slb.com (Bob Firestine)
Organization: Schlumberger ATE, San Jose, CA
Lines: 25

In article <2101@ucdavis.ucdavis.edu> hildum@iris.ucdavis.edu (Eric Hildum) writes:
<I am current using VAX/VMS C version 2.3-024.  Several of my programs
<dynamically allocate space which is later referenced using array
<reference syntax (eg, in a partial sketch: the variable is declared
<"double ****temp[3]" and later referenced with
<"temp[index][f][b][y][x]", after having been set to point at arrays of
<properly declared pointers).  I have no trouble when I compile the
<programs /NOOPTIMIZE, but get access violations when I compile
</OPTIMIZE.  The only time I have noticed the problem is when I
<reference the (declared) array in a loop where the loop variable is
<used as the index (ie, "index" in the above example).  Apparently the
<optimizer attempts to optimize the loop index - and screws up.

<Is there a later version of C that I can get, and is this a known
<problem - or should I submit an SPR?
>
We received version 2.4 about two days ago.

-------------------------------------------------------------------------------

Bob Firestine			firestine@M_sjs.sdr.slb.com
Schlumberger Technologies	bob%sjsca4@spar.slb.com
1601 Technology Drive 
San Jose CA 95115	
408-437-5216