Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!cs.utexas.edu!rutgers!mcnc!rti!xyzzy!poirier
From: poirier@dg-rtp.dg.com (Charles Poirier)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Aztec 5.0, watch out. . .
Summary: Long ints
Keywords: molassas
Message-ID: <3051@xyzzy.UUCP>
Date: 6 Feb 90 22:12:33 GMT
References: <42016@ames.arc.nasa.gov>
Sender: usenet@xyzzy.UUCP
Reply-To: poirier@dg-rtp.dg.com (  Poirier local)
Lines: 18

In article <42016@ames.arc.nasa.gov> mike@ames.arc.nasa.gov (Mike Smithwick) writes:
<Well, dang....
<
<So I timed a set of 3-D and planetary calculations for the 3.6 
<compiled version, 31 seconds...
<
<Then I install 5.0 (a real breeze BTW), recompile after making a few tweaks
<to the code, and rerun the thing. 38 seconds....
<
<My compiler options are : -ff  -so -wa -wr -wu  -pb -wn
<What gives?

I'm not sure I can parse those options, but is it possible you are
using the default size for ints in both cases?  As Aztec C 5.0 has
gone over to default 32 bit ints instead of 16 bit ints, this would
easily explain the loss of speed.

	Cheers,
	Charles Poirier