Name
f95parse — Shell scripts that executes the right parsers and IL analyzers
Synopsis
f95parse {
Fortran file
} [
-F
] [
-I
directory
] [
-M
directory
] [
-R
] [
-r
] [
-U
] [
-u
] [
-A
] [
-Llfile
] [
-o
pdbfile
]
Description
Fortran file is the source file for which a program database (PDB) file is generated. The filename of the PDB file will have the basename of the Fortran file and the suffix ".pdb".
You can also specify additional flags necessary for your program to compile. The configure script will determine most, if not all, flags and incorporate these in cparse. Local options, such as an application include directory, can be specified here.
Options
-v
Verbose flag. In this mode, all error messages and warnings
are displayed.
-R free
Specifies free form, -R fixed specifies fixed form for
the Fortran source code. If your Fortran source has a .f file
extension and uses free form, it is important to specify
this flag. By default the parser assumes fixed form for F77.
For other flags that f95parse accepts, please refer to the
etc/flint.hls file.
-p
invoke preprocessor.
-o<pdbfile>
Specifies the name of the PDB file. Note: there is
no space between -o and the file name.
Note
You may specify multiple fortran files on the command-line to resolve module dependencies. e.g.,
% f95parse `find . -name "*.f90" -print` -omerged.pdb
parses all files with .f90 suffix to produce merged.pdb file.
Currently, f95parse can produce PDB files that have enough information for use with the TAU profiling package. However, it does not have argument and calltree information that may be needed for other tools such as CHASM. This will be added in future releases.