🚀 go-pugleaf

In article <1768@ncoast.UUCP> btb@ncoast.UUCP (Brad Banko) writes:
>...
>	(	if (.not. (a.le.n) ) ..., should go to:
>		if ( a.gt.n ) ...	),
>
>	I don't know much about compilers.  Our Fortran compiler is
>Vax Fortran ...
>second, if the ratfor ( if (.not. (a.le.n))...) is hand optimized to
>( if (a.gt.n) ...) the resulting executable file runs twice as fast.


Hmm.  I've looked at the code VAX/VMS FORTRAN produces in the past.
The optimization always struck me as being very good.  Is this the
FORTRAN you are using, or do you use UNIX/Eunice?  Also, I assume
that either you are doing more hand-optimizations than just this
one line, or this is almost your entire routine in order for there
to be a difference-factor of 2 for this trivial change.  Could you be
so nice as to send us (or at least me) the Macro-11 the code produces?
I'm curious.  (In VAX/VMS FORTRAN, I think you want the /MACH option.
Don't do a /FULL list or anything like that).

Of course, it could be possible you've stumbled across just the right
combination of boolean operators to negate the compiler's ability to
optimize, at which point DEC would probably love to receive a fairly
detailed description....
-- 
UUCP: ihnp4!rosevax!dayton!joe          Joe Larson
ATT : (612) 375-3537                    Dayton Hudson Department Store Company
(standard disclaimer...)                700 on the Mall
                                        Mpls, Mn. 55408