For any given input file, the file name suffix determines what kind of compilation is done. The following kinds of input file names are supported:
Modula-2 implementation or program source files. See the -fmod= option if you wish to compile a project which uses a different source file extension.
Modula-2 definition module source files. Definition modules are not compiled separately, in GNU Modula-2 definition modules are parsed as required when program or implementation modules are compiled. See the -fdef= option if you wish to compile a project which uses a different source file extension.
You can specify more than one input file on the gm2 command line,
create debugging information so that debuggers such as gdb can inspect and control executable.
used to specify the search path for definition and implementation modules. An example is:
gm2 -g -c -I.:../../libs foo.mod. If this option is not specified then the default path is added which consists of the current directory followed by the appropriate language dialect library directories.
turns on auto initialization of pointers to NIL. Whenever a block is created all pointers declared within this scope will have their addresses assigned to NIL.
turns on run time subrange, array index and indirection via
turns on compile time checking to check whether a
CASEstatement requires an
ELSEclause when on was not specified.
preprocess the source with cpp -lang-asm -traditional-cpp For further details about these options If -fcpp is supplied then all definition modules and implementation modules which are parsed will be prepossessed by cpp.
call a real function, rather than the builtin equivalent. This can be useful for debugging parameter values to a builtin function as it allows users to single step code into an intrinsic function.
recognize the specified suffix as a definition module filename. The default implementation and module filename suffix is .def. If this option is used GNU Modula-2 will still fall back to this default if a requested definition module is not found.
display all inbuilt system items. This is an internal command line option.
turn on exception handling code. By default this option is on. Exception handling can be disabled by -fno-exceptions and no references are made to the run time exception libraries.
allows opaque types to be implemented as any type. This is a GNU Modula-2 extension and it requires that the implementation module defining the opaque type is available so that it can be resolved when compiling the module which imports the opaque type.
turns on run time checking to check whether a floating point number is about to exceed range.
attempt to find all modules when linking and generate a module list. If the filename is - then the contents are not written and only used to force the linking of all module ctors. This option cannot be used if -fuse-list= is enabled.
generate code to check whether array index values are out of bounds. Array index checking can be disabled via -fno-index.
turn on ISO standard features. Currently this enables the ISO
SYSTEMmodule and alters the default library search path so that the ISO libraries are searched before the PIM libraries. It also effects the behavior of
modifies the default library search path. The libraries supplied are: m2pim, m2iso, m2min, m2log and m2cor. These map onto the Programming in Modula-2 base libraries, ISO standard libraries, minimal library support, Logitech compatible library and Programming in Modula-2 with coroutines. Multiple libraries can be specified and are comma separated with precedence going to the first in the list. It is not necessary to use -flibs=m2pim or -flibs=m2iso if you also specify -fpim, -fpim2, -fpim3, -fpim4 or -fiso. Unless you are using -flibs=m2min you should include m2pim as the they provide the base modules which all other dialects utilize. The option -fno-libs=- disables the gm2 driver from modifying the search and library paths.
On systems that provide the m2 runtimes as both shared and static libraries, this option forces the use of the static version.
improve the debugging experience for new programmers at the expense of generating
nopinstructions if necessary to ensure single stepping precision over all code related keywords. An example of this is in termination of a list of nested
IFstatements where multiple
ENDkeywords are mapped onto a sequence of
render keywords in error messages using lower case.
specify the module mangled prefix name for all modules in the following include paths.
for internal use only: used by the driver to copy the user facing -I option.
insert plugin to identify run time errors at compile time (default on).
specify the module mangled prefix name. All exported symbols from a definition module will have the prefix name.
generates quadruple information: number of quadruples generated, number of quadruples remaining after optimization and number of source lines compiled.
experimental flag to turn on the new strict type checker.
compile all implementation modules and program module at once. Notice that you need to take care if you are compiling different dialect modules (particularly with the negative operands to modulus). But this option, when coupled together with
-O3, can deliver huge performance improvements.
recognize the specified suffix as implementation and module filenames. The default implementation and module filename suffix is .mod. If this option is used GNU Modula-2 will still fall back to this default if it needs to read an implementation module and the specified suffixed filename does not exist.
generate code to detect accessing data through a
NILvalue pointer. Dereferencing checking through a
NILpointer can be disabled by -fno-nil.
turn on PIM standard features. Currently this enables the PIM
SYSTEMmodule and determines which identifiers are pervasive (declared in the base module). If no other -fpim switch is used then division and modulus operators behave as defined in PIM4.
turn on PIM-2 standard features. Currently this removes
SIZEfrom being a pervasive identifier (declared in the base module). It places
SYSTEMmodule. It also effects the behavior of
turn on PIM-3 standard features. Currently this only effects the behavior of
turn on PIM-4 standard features. Currently this only effects the behavior of
MODoperators to behave as defined by PIM4. All modulus results are positive and the results from the division are rounded to the floor.
link against the pthread library. By default this option is on. It can be disabled by -fno-pthread. GNU Modula-2 uses the GCC pthread libraries to implement coroutines (see the SYSTEM implementation module).
generate code to check the assignment range, return value range set range and constructor range. Range checking can be disabled via -fno-range.
generate code to check that functions always exit with a
RETURNand do not fall out at the end. Return checking can be disabled via -fno-return.
specify, using a comma separated list, the run time modules and their order. These modules will initialized first before any other modules in the application dependency. By default the run time modules list is set to
m2iso:RTentity,m2iso:Storage,m2iso:SYSTEM, m2iso:M2RTS,m2iso:RTExceptions,m2iso:IOLink. Note that these modules will only be linked into your executable if they are required. Adding a long list of dependent modules will not effect the size of the executable it merely states the initialization order should they be required.
the option ensures that gm2 will generate a dynamic scaffold infrastructure when compiling implementation and program modules. By default this option is on. Use -fno-scaffold-dynamic to turn it off or select -fno-scaffold-static.
generate a C source scaffold for the current module being compiled.
generate a C++ source scaffold for the current module being compiled.
force the generation of the main function. This is not necessary if the -c is omitted.
the option ensures that gm2 will generate a static scaffold within the program module. The static scaffold consists of sequences of calls to all dependent module initialization and finalization procedures. The static scaffold is useful for debugging and single stepping the initialization blocks of implementation modules.
generate a shared library from the module.
turns on all run time checks. This is the same as invoking GNU Modula-2 using the command options
-fnil -frange -findex -fwholevalue -fwholediv -fcase -freturn.
displays the path to the source of each module. This option can be used at compile time to check the correct definition module is being used.
generate a swig interface file.
enable optimization of unbounded parameters by attempting to pass non
VARunbounded parameters by reference. This optimization avoids the implicit copy inside the callee procedure. GNU Modula-2 will only allow unbounded parameters to be passed by reference if, inside the callee procedure, they are not written to, no address is calculated on the array and it is not passed as a
VARparameter. Note that it is possible to write code to break this optimization, therefore this option should be used carefully. For example it would be possible to take the address of an array, pass the address and the array to a procedure, read from the array in the procedure and write to the location using the address parameter.
Due to the dangerous nature of this option it is not enabled when the -O option is specified.
if -fscaffold-static is enabled then use the file filename for the initialization order of modules. Whereas if -fscaffold-dynamic is enabled then use this file to force linking of all module ctors. This option cannot be used if -fgen-module-list= is enabled.
generate code to detect whole number division by zero or modulus by zero.
generate code to detect whole number overflow and underflow.
generate a warning if a
CASEstatement selects on an enumerated type expression and the statement is missing one or more
CASElabels. No warning is issued if the
CASEstatement has a default
ELSEclause. The option -Wall will turn on this flag.
issue a warning if a variable is used before it is initialized. The checking only occurs in the first basic block in each procedure. It does not check parameters, array types or set types.
issue a warning if a variable is used before it is initialized. The checking will only occur in the first basic block in each procedure if known is specified. If cond or all is specified then checking continues into conditional branches of the flow graph. All checking will stop when a procedure call is invoked or the top of a loop is encountered. The option -Wall will turn on this flag with -Wuninit-variable-checking=known. The -Wuninit-variable-checking=all will increase compile time.
gpl(7), gfdl(7), fsf-funding(7), gcc(1) and the Info entries for gm2 and gcc.
Copyright (c) 1999-2024 Free Software Foundation, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the man page gfdl(7).