Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!mit-amt!peter
From: peter@mit-amt.MEDIA.MIT.EDU (Peter Schroeder)
Newsgroups: comp.sys.hp
Subject: Re: Possible HP-UX compiler optimizer bug (found while making Perl)
Message-ID: <1001@mit-amt.MEDIA.MIT.EDU>
Date: 10 Nov 89 18:08:43 GMT
References: <4413@fmeed1.UUCP> <4432@fmeed1.UUCP>
Reply-To: peter@media-lab.media.mit.edu (Peter Schroeder)
Organization: MIT Media Lab, Cambridge MA
Lines: 34

In article <4432@fmeed1.UUCP> wehr@fmeed1.UUCP (Bruce Wehr) writes:
>	1) edit config.sh: change optimize from -O to +O1

I have had problems too with using the -O flag and could fix them by
going to +O1. What am I actually loosing by not getting the +O2 optimizations?
I noticed that the difference between -g and -O can be amazing when it
comes to speed, so I am reluctant to give up any optimizations.

Concretely the problems have been errors of the form:

cc: Ncolor: Out of memory: get_wbset. (6284)
cc: Bit vectors: Set out of memory. (6355)
cc: Ncolor: Out of memory: init. (6281)
cc: Aliaser: Out of memory. (6200)
cc: Local dataflow: Out of memory. (6270)

(One time the compiler actually printed something to the effect that I
should call HP...)

What do these mean? I noticed in the man page for cc that for the 300
series you can set various obscure limits inside cc with command line
switches (and we used those at times to compile very large things) but
apparently these switches are not supported on the 800 (which is what
I am using, version 3.1). Are the hidden switches that could help me
to get around problems of the above kind?

BTW, all these errors occured when building cfront 2.0, if you are
interested in more details, mail me.

Thanks for your help!


Peter
peter@media-lab.media.mit.edu