🚀 go-pugleaf

> Minor Flame Start {
> Can anyone think of any good reason why the optimiser is permanantly ON in
> the C compiler? Every other C compiler on the planet has the optimiser as an
> optional command line flag... Is it really just to make the dhrystone results
> look better (as the benchmark specifies that the compiler should be run in
> it's default state--optimiser off for everyone else, but on for the Acorn one)
> } Minor Flame End
> 


 Major Flame Start {

UG! 

Harrumph... I suspected the optimiser was on..... 

It makes debugging/tracing ARRAYS (matricies) and other such variables a 
MAJOR BUMMER. (i.e after an array as been through a function, one gets results 
1.9876735664 E+238.....)

I compiled a proglet (a numerical analysis using (vectorial) Lax-Wendroff 
F-D scheme) on the VAX with optimize on and got similar results to debugging 
on the Archie [ made a hell of a difference when I turned the optimiser off!] 

I also suspect this may be the reason the flaming debugger on the Arc changes 
the program enviroment; stuffing the &^^$$#$@#'ing results!

} Major Flame End.

From Martin Glanvill		(mcg@waikato.ac.nz)

Dept. Maths 							      @@@@@/|@
University of Waikato						      @@@@/ |@
Hamilton							      @@@/__|@
New Zealand							      @@/   |@
								      @@@@@@@@

----------------****=====| A quote to make your day |======****-----------------
Any philosophy that can be put in a nutshell belongs there.
                                        -- Sydney J. Harris
-------------------------------------------------------------------------------