Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!dog.ee.lbl.gov!me10.lbl.gov!milburn From: milburn@me10.lbl.gov (John Milburn) Newsgroups: comp.sys.hp Subject: Re: cc optimizer dies on a few perl.4.0.beta files Message-ID: <11330@dog.ee.lbl.gov> Date: 22 Mar 91 17:46:50 GMT References: Reply-To: JEMilburn@lbl.gov (John Milburn) Distribution: comp Organization: Lawrence Berkeley Laboratory, Berkeley Lines: 24 X-Local-Date: Fri, 22 Mar 91 09:46:50 PST beshers@cs.columbia.edu (Clifford Beshers) writes: >In article <11307@dog.ee.lbl.gov> milburn@me10.lbl.gov (John Milburn) writes: > Gee, the same thing happened with perl rev 3. Give yourself enough > swap and enough user memory, an a LOT of time, and you really can > optimize eval.c and toke.c. At least you could with 3.0. >This isn't enough? > Physical memory: 32768 Maximum user memory: 28972 > Free memory: 23692 User memory utilization: 18% > Swap space configured: 43008 Enabled via swapon(1m): 43008 > Currently free swap space: 34120 Swap space utilization: 20% No, its not. I needed about 80 Megs of swap to optimize eval.c. I only did it once, then switched to +O1 for eval.c and toke.c. I guess the -O level of optimization in hp-ux is over ambitious. -jem -- John Milburn milburn@me10.lbl.gov (415) 486-6969 "I am successful because I am the only person in my city who is not heavily addicted to powerful narcotics." -Cerebus