[MLton-devel] nucleic benchmark times

[Matthew Fluet]

> One thing to be cautious about in Matthew's numbers (which are great) is which
> version of gcc was used.  We should to the run with at least gcc 3.2, and
> possibly with gcc 3.3 just to make sure that things haven't changed there.
> I know that gcc 2.96 did some really weird things in local code generation that
> only make sense on 386's, nothing higher level.  Thus one of the newer versions,
> with at least -mcpu=i686 (which tells it to schedule assuming a 686, but the
> code will runn on 386 or better) would be worth checking.

Good point.  It was:
[fluet@cfs21 ~ 4]% gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)



-------------------------------------------------------
This sf.net email is sponsored by: Are you worried about 
your web server security? Click here for a FREE Thawte 
Apache SSL Guide and answer your Apache SSL security 
needs: http://www.gothawte.com/rd523.html
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel