debian man page for tau_ompcheck

Query: tau_ompcheck

OS: debian

Section: 1

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

TAU_OMPCHECK(1) 						       Tools							   TAU_OMPCHECK(1)

NAME
tau_ompcheck - Completes uncompleted do/for/parallel omp directives
SYNOPSIS
tau_ompcheck {pdbfile} {sourcefile} [-o outfile] [-v] [-d]
DESCRIPTION
Finds uncompleted do/for omp directives and inserts closing directives for each one uncompleted. do/for directives are expected immediately before a do/for loop. Closing directives are then placed immediately following the same do/for loop.
OPTIONS
pdbfile A pdbfile generated from the source file you wish to check. This pdbfile must contain comments from which the omp directives are gathered. See pdbcomment for information on how to obtain comment from a pdbfile. sourcefile A fortran, C or C++ source file to analyzed. -o write the output to the specified outfile. -vverbose output, will say which directive where added. -d debuging information, we suggest you pipe this unrestrained output to a file.
EXAMPLES
To check file: source.f90 do: (you will need pdtoolkit/<arch>/bin and tau/utils/ in your path). %>f95parse source.f90 %>pdbcomment source.pdb > source.comment.pdb %>tau_omp source.comment.pdb source.f90 -o source.chk.f90
SEE ALSO
f95parse pdbcomment 04/27/2006 TAU_OMPCHECK(1)
Related Man Pages
xgettext(1) - opensolaris
cython(1) - debian
lgfile(5) - debian
unifdef(1) - netbsd
unifdefall(1) - netbsd
Similar Topics in the Unix Linux Community
&quot;make&quot; fails on the first .f90 file it encounters: not creating .o files
Help with make this Fortran code more efficient (in HPC manner)
Datatype and length validation
Strange characters in FORTRAN code output
Use #if not defined with OR boolean logic in preprocessor directives