opari2(1)

💖 opari2 — bestie's guide to the OpenMP instrumentor 💖

okay so real quick, the header situation: this page lives in the General Commands Manual, and it's the manual page for opari2(1). but the tool itself is called opari, and she is ✨ iconic ✨. buckle up, we're instrumenting. 🎀

🌸 NAME 🌸

opari — a source to source OpenMP program instrumentor. she takes your code and adds the little measurement sparkles. periodt.

🦋 SYNOPSIS 🦋

opari
   [-f70|-f90|-c|-c++]
   [-disable <construct>[,<construct>]...]
   [-rcfile file] [-table <tabfile>] <infile> [<outfile>]
opari
   [-rcfile <file>] -table <tabfile>

like, that's the whole vibe. two whole modes. 💅

✨ DESCRIPTION ✨

so before you go compiling the source files of an OpenMP application, every single file needs to be transformed by a call to the OPARI tool. no skipping, bestie, this is not optional. 🫶

and then — and then — the application has to be linked against the pomp runtime measurement library and the OPARI runtime table file. that table file? you don't just find it lying around. it has to be generated by using the -table option to OPARI, and you have two routes:

• together with the transformation of the last input source file, or
• with a separate call to OPARI after all the transformations are done.

if the output file name is not specified, OPARI uses the name infile.mod.suffix when the input file is called infile.suffix. yes, she names it herself. main character energy. 👑

🌈 OPTIONS 🌈

• -f70, -f90, -c, -c++ — [OPTIONAL] tells OPARI what programming language your input source file is written in. lowkey only needed if the automatic language detection based on the input file suffix fails on you. 🙈
• -rcfile <file> — [OPTIONAL] by default OPARI uses the file ./opari.rc to preserve state information between calls to OPARI, which matters when your OpenMP application consists of more than one source file. with the -rcfile option, the file file is used instead. this is super 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 one 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 transformation of the last input source file, or with a separate call to OPARI after all transformations are done. no other options, bestie, those are the rules. 🔥
• -disable <construct> — [OPTIONAL] disable the instrumentation of the more fine-grained OpenMP constructs, such as !$OMP ATOMIC. constructs is a comma separated 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. so much power in one little flag. 💅

👀 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 others). 🫶

okay final vibe check, bestie: this page is from May 20, it's the opari2(1) manual, and that's a wrap. go forth and instrument. 🌸🦋💖