mlton usage message
Stephen Weeks
MLton@sourcelight.com
Thu, 21 Jun 2001 18:18:24 -0700
Here are what the new usage messages look like.
% mlton/bin/mlton
must supply a file
usage: mlton [option ...] file.{cm|sml|c|o} [file.{S|o} ...] [library ...]
-detect-overflow {true|false} overflow checking on integer arithmetic
-Ddefine define symbolic constant
-h heapSize [{k|m}] heap size used by executable
-iinclude include a .h file in the C code
-inline n inlining threshold
-Idir search dir for include files
-keep {cps|g|il|o|sml} save intermediate files
-llibrary link with a library
-Ldir search dir for libraries
-native {true|false} use native x86 code generator
-ieee-fp {false|true} use strict IEEE floating-point
-polyvariance {true|false} use polyvariance
-o file name of output file
-p produce executable with profiling info
-safe {true|false} bounds checking and other checks
-show-basis display the basis library
-static produce a statically linked executable
-stop {f|g|o|sml} where to stop
-v[0123] how verbose to be about compiler passes
mlton: failure
% mlton/bin/mlton -v -z
invalid switch: -z
usage: mlton [option ...] file.{cm|sml|c|o} [file.{S|o} ...] [library ...]
-detect-overflow {true|false} overflow checking on integer arithmetic
-Ddefine define symbolic constant
-g produce executable with debug info
-h heapSize [{k|m}] heap size used by executable
-iinclude include a .h file in the C code
-indentation n indentation level in ILs
-inline n inlining threshold
-Idir search dir for include files
-keep {cps|g|il|o|sml} save intermediate files
-llibrary link with a library
-Ldir search dir for libraries
-native {true|false} use native x86 code generator
-native-commented n ?level of comments (0)
-native-copy-prop {true|false} use copy propagation
-ieee-fp {false|true} use strict IEEE floating-point
-native-live-transfer {true|false} use live transfer
-native-move-hoist {true|false} use move hoisting
-native-optimize n level of optimizations
-native-split n ?split assembly files at ~n lines
-polyvariance {true|false} use polyvariance
-o file name of output file
-p produce executable with profiling info
-print-at-fun-entry print debuggin message at every call
-safe {true|false} bounds checking and other checks
-show-basis display the basis library
-show-types {false|true} print types in ILs
-static produce a statically linked executable
-stop {f|g|o|sml} where to stop
-trace name1,... trace compiler internals
-use-basis-library {true|false} prefix the basis library to the program
-v[0123] how verbose to be about compiler passes
mlton: failure