ContentsIndexPreviousNext

3.2.4 Generating Native Code From ACUCOBOL-GT Portable Code

The compiler utility program cblutil has an additional function, "-native", that allows you to translate ACUCOBOL-GT portable object modules into native-code object modules. The "-native" option has the following format:

cblutil -native [options] object-files ...

'Options' can be any of the following:

--intel produces 32-bit native code for Intel-class processors (386, 486, Pentium, Pentium II, Pentium III or compatible processors).

--sparc produces 32-bit native code for Sparc (v7 - v9) processors.

-o names the output file. This option must be followed (as a separate argument) by the name of the file to produce. You may use "@" in this name to stand for the base name of the input object file. If you specify "-o" and multiple object files, then you must use "@" in the name. If you omit "-o", then the output file replaces the input file.

-v causes cblutil to print the name of each object file as it is being processed.

-Zc produces code that is more compact and somewhat slower.

-Zn turns off the more involved optimizations. This is generally done only if you suspect a bug in the optimizer.

If you specify multiple object files, then each one is translated in turn. If 'object file' refers to an object library, then each module contained in the library is translated.

If you do not specify a target processor, then cblutil translates for the processor of the host machine.


Note that once you translate an object file to native code, it cannot be retranslated to use a different instruction set. If you translate an object file that contains debugging information, that information is retained in the file.
The cblutil option "-info" will print out the instruction set used in a particular object module if it is not the ACUCOBOL-GT portable instruction set.