[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.
>
> Matthew, can you rerun MLton{4,5,6} with gcc 2.96 vs gcc 3.2
> -mcpu=i686 (and 3.3 if you really want)?

Not easily.  I run those on the Linux cluster administered by the dept.,
and they are stock RH7.3 machines.  I could request gcc 3.2 to be
installed, but it wouldn't be any time soon.  And I don't know how happily
gcc would run out of my home directory.



-------------------------------------------------------
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