Tonto | ||
---|---|---|
<< Previous | Next >> |
There are two distinct ways to customise TONTO: by altering compiler flags, or by altering C-preprocessor macros.
If you are a programmer, or of you need to port TONTO to another platform, you should read this chapter.
If you are a user, it still might be convenient to have several versions of a TONTO program. For example, you might might want one version which is highly optimised, to be used for production calculations; and you might want another version compiled with no optimisation and full memory management and error checking turned on, to be used for code development or testing input decks.
By altering compile options, you can make versions with
high optimisation (this is the default)
high optimisation and profiling
no optimisation and debugging switches
different mathematical libraries
different compilers on the same platform
By altering certain C-preprocessor macros you can make versions of TONTO which will
Issue error messages labelled with their calling routine when anticipated problems are detected (turned on by default)
Issue error messages labelled with their calling routine when certain preconditions for executing a routine are not satisfied (turned off by default).
Issue a full routine call-stack traceback when an error condition is detected; and at the same time issue error messages when routines contain unintentional memory leaks (turned off by default)
Generate a version of TONTO which reverts to Fortran90 language definitions (turned off when the compiler is Fortran95 compliant)
Generate a version of TONTO which does not use derived type initialisation (turned off when the compiler is Fortran95 compliant)
<< Previous | Home | Next >> |
Communication and data storage in TONTO | Which Fortran compiler options to use? |