Path: utzoo!attcan!uunet!hi-csc!giebelhaus From: giebelhaus@hi-csc.UUCP (Timothy R. Giebelhaus) Newsgroups: comp.sys.apollo Subject: Re: Paranoia test, and some interesting results Message-ID: <4041b1d5.12c4f@hi-csc.UUCP> Date: 14 Dec 88 21:01:00 GMT References: <8812130122.AA21360@caesar.cs.montana.edu> Reply-To: giebelhaus@hi-csc.UUCP (Timothy R. Giebelhaus) Organization: csdd Lines: 31 In article <8812130122.AA21360@caesar.cs.montana.edu> icsu6000@CAESAR.CS.MONTANA.EDU (Mathisen) writes: > > Only one machine passed the test, out of the 3 I tried it on, and >that was a mVAX II running Ultrix 2.3, both the Apollo and an HP9000/350 SRX >crapped out. I am suspicious. Have you given an example of this to Apollo? Have you used the debugger to find out where the program is? Have you used the tb (trace back) command to see where the program is? Does your program get through lint? It is not my experience that the C compiler is so easy to break. If you think you have found a bug, please file an apr or ucr to report it (do a help on crucr or a man on mkapr if you are not sure how to report a bug). >[...] I'm suprised >by the pathetic compilation speed of the 3500, sounds like some serious >C compiler work is needed here. Did you use the /com/cc or /bin/cc? /com/cc will default to doing some optimization. As you know, this will take longer. The documentation for /com/cc states that the default optimization is 3 on a 0 to 4 scale where 4 is the highest level of optimization. >I'd be happy to send the source to anybody who wants it. I want to be sure Apollo gets a copy of the code. If your sales person is uninterested, you do not wish to place an APR, and you do not have a service contract to call the help line, please send the code to me so I can enter an APR myself. -- UUCP: uunet!hi-csc!giebelhaus UUCP: tim@apollo.uucp ARPA: hi-csc!giebelhaus@umn-cs.arpa ARPA: tim@apollo.com Tim Giebelhaus, Apollo Computer, Regional Software Support Specialist. My comments and opinions have nothing to do with work.