Invoking otmc

otmc understands the following options:

-dgc number

Define the debugging verbosity of the garbage collector used within the compiler. By default the garbage collection is turned off, which is equal to -dgc-1. To enable it without debugging information, supply -dgc 0. You normally do not enable gc.

-flookup-direct

-flookup-lookup

-flookup-send

Determine how method invocations are dispatched. The default dispatch mechanism depends on the machine otmc is running on, but for a mature port it probably is -flookup-send. See section Message dispatching for more information.

-fsuper-direct

-fsuper-lookup

-fsuper-send

Determine how invocations to super are dispatched. The default is either -fsuper-lookup or -fsuper-send, again depending on the machine. -fsuper-send is not possible on machines which pass some of the arguments in registers.

-fatomic-gc

-fincremental-gc

Define whether the code to be compiled can assume atomic garbage collection runs. With this assumption, an assignment to a class or instance variable incurs no overhead. An atomically garbage collected program consumes, on average, about half the memory of an incrementally collected program, since when using incremental gc, a dead object is not reclaimde by the end of the next run that is completed. With atomic gc, it will be reclaimed by the end of this run. The default is incremental gc. For units that are distributed in a binary (non-source) form, atomic gc should never be assumed. [Note: Currently, the runtime does not actually take advantage of any atomicity in the garbage collection runs. End note.]

-precious

Do not remove the output file, even in the case of errors.

-Wempty

Warn about empty expressions. This is the default.

-Wno-empty

Do not warn about empty expressions.

Go to the first, previous, next, last section, table of contents.