[MLton-user] Performances: mlton 20030716p1 V.S. 20051202

[Alexandre Langenieux]

Hello,

We are currently running mlton-20030716p1 and we want to migrate to the 
last version
mlton-20051202.

Unfortunately, we are facing some high performances regression using 
this new release
(something around 60%) compare to our current version.

We are compiling with the following options for mlton-20051202:
mlton -codegen native -const "Exn.keepHistory true" -verbose 2 \
      -native-split 100000 -cc-opt -s -cc-opt -freg-struct-return \
      -cc-opt -funroll-all-loops -align 4 -cc-opt -O2 -polyvariance false \
      -inline 5 -cc-opt -D_UNIX -link-opt "-L ../lib/linux" -link-opt 
"-L ../lib/linux/libc2.1" \
      -link-opt -lpst -link-opt -lwk-lin  \
      -output a.out sources.mlb file.c

And for the version mlton-20030716p1:
mlton -cc-opt -D_UNIX -verbose 1 -text-io-buf-size 65536 \
      -safe true -exn-history true -detect-overflow false -basis 1997 \
      -may-load-world false -native-split 100000 -cc-opt -s \
      -cc-opt -freg-struct-return -cc-opt -funroll-all-loops -align 4 \
      -polyvariance false -inline 5 -lib-search . -link pst -link wk-lin \
      -output a.out file.sml file.c

Are we missing some optimizations switches ?
Does the fact to compile a big defunct sml file can change things on 
performances
instead of compiling files with mlb ?

Thanks for your help.