compiling VAX C with & w/o nooptimize

[Pat Rankin]

In article <BB3_R!F at cs.widener.edu>, brendan at cs.widener.edu (Brendan Kehoe) writes...
>In <16550 at chaph.usc.edu>, sgee at sal-sun4.usc.edu writes:
>>     and for some reason or other, if i do not compile
>>     my server end with the option "nooptimize", the 
>>     s/w does not successfully create the network object
>>     on the server node.   
> 
>   I seem to remember reading somewhere (the Emacs build?) that the
>   optimizer for the Vax C compiler's broken (not sure if it's been
>   fixed in the recent update or not); to avoid the problems, do:
>		CC/OPTIMIZE=NOINLINE
>   Give that a try & see if it works.

     That's highly recommended for VAX C V3.0; it's probably not necessary
for V3.1 and later.  However, it's not allowed for V2.4 and earlier, so it
can't be used blindly.  CC/NOOPTIMIZE will work for any release. :-}
Note that /OPTIMIZE=(DISJOINT,INLINE) is the default for VAX C for V3.x,
and /OPTIMIZE (there were no class keywords then) was the default for
V2.x and presumeably for V1.x.  Digital turns on optimization by default
for most or all of their VMS compilers.

     It you suspect that the optimizer is generating bad code--since
disabling it gives working code, I'd suspect that--you can produce a
compiler listing and examine that.  CC/LIST/MACHINE will show the code
that's being generated, interleaved with the original source code.

     The current version of VAX C is V3.2.  There's not too much point
hunting for compiler bugs in older releases, unless you're forced to
stick with obsolete software.

		Pat Rankin, rankin at eql.caltech.edu