Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

opari(1) [debian man page]

opari(1)						      General Commands Manual							  opari(1)

NAME
opari - source to source OpenMP program instrumentor SYNOPSIS
opari [-f70|-f90|-c|-c++] [-disable <construct>[,<construct>]...] [-rcfile file] [-table <tabfile>] <infile> [<outfile>] opari [-rcfile <file>] -table <tabfile> DESCRIPTION
Before compiling the source files of an OpenMP application, each file needs to be transformed by a call to the OPARI tool. In addition, the application has to be linked against the pomp runtime measurement library and the OPARI runtime table file. The latter has to be generated by using the -table option to OPARI either together with the transformation of the last input source file or with a separate call to OPARI after all transformations are done. If the output file name is not specified, OPARI uses the name infile.mod.suffix if the input file is called infile.suffix. OPTIONS
-f70, -f90, -c, -c++ [OPTIONAL] Specifies the programming language of the input source file. This option is only necessary if the automatic language detection based on the input file suffix fails. -rcfile <file> [OPTIONAL] OPARI uses the file ./opari.rc to preserve state information between calls o OPARI if the OpenMP application consists of more than one source file. With the -rcfile option the file file is used instead. This can be useful if more than one application is stored in the same directory or if the source files of an application are stored in more than more directory. -table <tabfile> Generate the OPARI runtime table in file tabfile. This option has to be used either together with the call to OPARI for the trans- formation of the last input source file or with a separate call to OPARI after all transformations are done. -disable <construct> [OPTIONAL] Disable the instrumentation of the more fine-grained OpenMP constructs such as !$OMP ATOMIC. constructs is a comma sepa- rated list of the constructs for which the instrumentation should be disabled. Accepted tokens are atomic, critical, master, flush, single, or locks as well as sync to disable all of them. SEE ALSO
/usr/share/doc/opari/Readme.html AUTHOR
opari was written by Bernd Mohr. This manual page was adapted from Readme.html by Samuel Thibault <sthibault@debian.org>, for the Debian project (and may be used by oth- ers). May 20 opari(1)

Check Out this Related Man Page

GXL2GV,GV2GXL(1)					      General Commands Manual						  GXL2GV,GV2GXL(1)

NAME
gxl2gv,gv2gxl - GXL-GV converters SYNOPSIS
gxl2gv [ -gd? ] [ -ooutfile ] [ files ] gv2gxl [ -gd? ] [ -ooutfile ] [ files ] DESCRIPTION
gxl2gv converts between graphs represented in GXL and in the GV language. Unless a conversion type is specified using a flag, gxl2gv will deduce the type of conversion from the suffix of the input file, a ".gv" suffix causing a conversion from GV to GXL, and a ".gxl" suffix causing a conversion from GXL to GV. If no suffix is available, e.g. when the input is from a pipe, and no flags are used then gxl2gv assumes the type of the input file from its executable name so that gxl2gv converts from GXL to GV, and gv2gxl converts from GV to GXL. GXL supports a much richer graph model than GV. gxl2gv will attempt to map GXL constructs into the analogous GV construct when this is pos- sible. If not, the GXL information is stored as an attribute. The intention is that applying gxl2gv|gv2gxl is semantically equivalent to the identity operator. OPTIONS
The following options are supported: -g The command name and input file extensions are ignored, the input is taken as a GV file and a GXL file is generated. -d The command name and input file extensions are ignored, the input is taken as a GXL file and a GV file is generated. -? Prints usage information and exits. -o outfile If specified, the output will be written into the file outfile. Otherwise, output is written to standard out. OPERANDS
The following operand is supported: files Names of files containing 1 or more graphs in GXL or GV. If no files operand is specified, the standard input will be used. RETURN CODES
Both gxl2gv and gv2gxl return 0 if there were no problems during conversion; and non-zero if any error occurred. BUGS
gxl2gv will only convert in one direction even if given multiple files with varying suffixes. The conversion can only handle one graph per GXL file. There are some GXL constructs which gxl2gv cannot handle. AUTHORS
Krishnam Pericherla <kp@research.att.com> Emden R. Gansner <erg@research.att.com> SEE ALSO
dot(1), libgraph(3), libagraph(3), neato(1), twopi(1) 20 December 2002 GXL2GV,GV2GXL(1)
Man Page