PETSc Style and Usage Guide#

The PETSc team uses certain conventions to make the source code consistent and hence easier to maintain. We will interchangeably use the terminology subclass, implementation, or type 1 to refer to a concrete realization of an abstract base class. For example, KSPGMRES is a type for the base class KSP.


Consistency of names for variables, functions, and so on is extremely important. We use several conventions

  1. All function names and enum types consist of acronyms or words, each of which is capitalized, for example, KSPSolve() and MatGetOrdering().

  2. All enum elements and macro variables are named with all capital letters. When they consist of several complete words, there is an underscore between each word. For example, MAT_FINAL_ASSEMBLY.

  3. Functions that are private to PETSc (not callable by the application code) either

    • have an appended _Private (for example, StashValues_Private) or

    • have an appended _Subtype (for example, MatMultSeq_AIJ).

    In addition, functions that are not intended for use outside of a particular file are declared static. Also see item on symbol visibility in Usage of PETSc Functions and Macros.

  4. Function names in structures (for example, _matops) are the same as the base application function name without the object prefix and are in small letters. For example, MatMultTranspose() has a structure name of multtranspose.

  5. Names of implementations of class functions should begin with the function name, an underscore, and the name of the implementation, for example, KSPSolve_GMRES().

  6. Each application-usable function begins with the name of the class object, followed by any subclass name, for example, ISInvertPermutation(), MatMult(), or KSPGMRESSetRestart().

  7. Functions that PETSc provides as defaults for user-providable functions end with Default (for example, PetscSignalHandlerDefault()).

  8. Options database keys are lower case, have an underscore between words, and match the function name associated with the option without the word “set” or “get”, for example, -ksp_gmres_restart.

  9. Specific XXXType values (for example, MATSEQAIJ) do not have an underscore in them unless they refer to another package that uses an underscore, for example, MATSOLVERSUPERLU_DIST.

Coding Conventions and Style#

Within the PETSc source code, we adhere to the following guidelines so that the code is uniform and easily maintained.

C Formatting#

  1. No tabs are allowed in any of the source code.

  2. All PETSc function bodies are indented two characters.

  3. Each additional level of loops, if statements, and so on is indented two more characters.

  4. Wrapping lines should be avoided whenever possible.

  5. Source code lines do not have a hard length limit; generally, we like them less than 150 characters wide.

  6. The local variable declarations should be aligned. For example, use the style

    instead of

    PetscScalar a;
    PetscInt i,j; /* Incorrect */
  7. Assignment and comparison operations, for example, x = 22.0 or x < 22.0, should have single spaces around the operator. This convention is true even when assignments are given directly in a line that declares the variable, such as PetscReal r = 22.3. The exception is when these symbols are used in a for loop; then, there should be no spaces, for example, for (i=0; i<m; i++). Comparisons in while() constructs should have the spaces.

  8. When declaring variables there should be no space between multiple variables, for example, PetscReal a,b,c, not PetscReal a, b, c.

  9. The prototypes for functions should not include the names of the variables

    PETSC_EXTERN PetscErrorCode MyFunction(PetscInt); // Correct
    PETSC_EXTERN PetscErrorCode MyFunction(PetscInt myvalue); // Incorrect
  10. All local variables of a particular type (for example, PetscInt) should be listed on the same line if possible; otherwise, they should be listed on adjacent lines. Note that pointers of different arity are considered to be different types

    // Correct
    PetscInt a,b,c;
    PetscInt *d,*e;
    PetscInt **f;
    // Incorrect
    PetscInt a,b,c,*d,*e,**f;
  11. Equal signs should be aligned in regions where possible, but are allowed to not be aligned across comments, empty lines, or preprocessor directives.

    // Correct
    bob   = 1;
    alice = 2;
    // Correct, broken by an allowed delimiter
    bob = 1;
    alice = 2;
    bob = 1;
    // a very instructive comment
    alice = 2;
    // Incorrect
    bob = 1;
    alice = 2;
  12. There must be a single blank line between the local variable declarations and the body of the function.

    // Correct
    PetscInt x;
    // Incorrect
    PetscInt x;
  13. All PETSc functions must have their return value checked for errors using the PetscCall() macro. This should be wrapped around the function in question.

    PetscCall(MyFunction(...)); // Correct
    PetscErrorCode ierr = MyFunction(...);PetscCall(ierr); // Incorrect

    The only exceptions to this rule are begin-end style macros which embed local variables or loops as part of their expansion (e.g. PetscOptionsBegin()/PetscOptionsEnd()). These should assign to ierr and place the PetscCall() call immediately afterwards on the same line

    // Correct
    ierr = PetscOptionsBegin(...);PetscCall(ierr);
    ierr = PetscOptionsEnd();PetscCall(ierr);
    // Incorrect

    As a rule, always try to wrap the function first, only if this fails to compile may you consider the trailing style.

  14. Indentation for if statements must be done as follows.

    if ( ) {
    } else {
  15. Never have

    if ( )
      a single indented line /* Incorrect */


    for ( )
      a single indented line /* Incorrect */

    Instead, use either

    if ( ) a single statement


    if ( ) {
      a single indented line

    Note that error checking is a complete statement, so should be put inline with the if statement

    if ( ) {
      PetscCall(XXX()); /* Incorrect */
    if ( ) PetscCall(XXX()); /* Correct */
  16. Always have a space between if or for and the following ().

  17. The open brace should be on the same line as the if ( ) test, for ( ), and so forth, not on its own line, for example,

    } else {

    instead of

    else { /* Incorrect */

    See the next item for an exception. The closing brace should always be on its own line.

  18. In function declarations, the opening brace should be on the next line, not on the same line as the function name and arguments. This is an exception to the previous item.

    // Correct
    PetscErrorCode Foo(...)
    // Incorrect
    PetscErrorCode Foo(...) {
  19. Do not leave sections of commented-out code in the source files.

  20. Use classic block comments (/* Comment */) for multi-line comments, and // Comment for single-line comments in source files.

  21. All variables must be declared at the beginning of the code block (C89 style), never mixed in with code. When variables are only used in a limited scope, it is encouraged to declare them in that scope. For example:

    if (cond) {
      PetscScalar *tmp;
      // use tmp

    The only exception to this variables used exclusively within a for loop, which must be declared inside the loop initializer:

    // Correct
    for (PetscInt i=0; i<n; ++i) {
      // loop body
    // Correct, variable used outside of loop
    PetscInt i;
    for (i=0; i<n; ++i) {
      // loop body
    j = i;
    // Incorrect
    PetscInt i;
    for (i=0; i<n; ++i) {
      // loop body
  22. Do not include a space after a ( or before a ). Do not write

    PetscCall(PetscMalloc1( 10,&a )); /* Incorrect */

    but instead write

  23. Do not use a space after the ) in a cast or between the type and the * in a cast.

    // Correct
    // Incorrect
    (PetscInt) x;
    (PetscInt *)y;
  24. Do not include a space before or after a comma in lists. That is, do not write

    PetscCall(func(a, 22.0)); /* Incorrect */

    but instead write


C Usage#

  1. Array and pointer arguments where the array values are not changed should be labeled as const arguments.

  2. Scalar values passed to functions should never be labeled as const.

  3. Subroutines that would normally have a void** argument to return a pointer to some data should actually be prototyped as void*. This prevents the caller from having to put a (void**) cast in each function call. See, for example, DMDAVecGetArray().

  4. Do not use the register directive.

  5. Do not use if (v == NULL) or if (flg == PETSC_TRUE) or if (flg == PETSC_FALSE). Instead, use if (!v) or if (flg) or if (!flg).

  6. Do not use #ifdef or #ifndef. Rather, use #if defined(... or #if !defined(.... Better, use PetscDefined() (see below). The only exception to this rule is for header guards, where the #ifndef form is preferred (see below).

  7. Header guard macros should include the full name and end in _FILE_EXTENSION of the file and be formed using #ifndef. For example:

    // my_petsc_header_file.h
    #endif // MY_PETSC_HEADER_FILE_H
  8. Never use system random number generators such as rand() in PETSc code or examples because these can produce different results on different systems thus making portability testing difficult. Instead use PetscRandom which produces the exact same results regardless of system it is used on.

  9. Variadic macros may be used in PETSc, but must work with MSVC v1900+ (Visual Studio 2015). Most compilers have conforming implementations of the C99/C++11 rules for __VA_ARGS__, but MSVC’s implementation is not conforming and may need workarounds. See PetscDefined() for an example of how to work around MSVC’s limitations to write a macro that is usable in both.

  10. Do not use language features that are not in the intersection of C99, C++11, and MSVC v1900+ (Visual Studio 2015). Examples of such features include variable-length arrays. Note that variable-length arrays (including VLA-pointers) are not supported in C++ and were made optional in C11. You may use designated initializers via the PetscDesignatedInitializer() macro.

Usage of PETSc Functions and Macros#

  1. Lengthy conditional preprocessor blocks should mark any #else or #endif directives with a comment containing (or explaining) either the boolean condition or the name of the macro if the first directive is testing whether one is defined. One should be able to read any part of the macro block and be able to find or deduce the initial #if. That is:

    #if defined(MY_MACRO)
    // many lines of code
    #else // MY_MACRO (use name of macro)
    // many more lines of code
    #endif // MY_MACRO
    #if MY_MACRO > 10
    // code
    #else // MY_MACRO < 10
    // more code
    #endif // MY_MACRO > 10
  2. Nested preprocessor blocks should be indent the text (not the #) following the normal indentation rules outlined above. For example:

    // Right
    #if MY_VARIABLE > 10
    #  if MY_OTHER_VARIABLE > 15
    #    define BIG_VARIABLE 1
    // Wrong
    #if MY_VARIABLE > 10
      #if MY_OTHER_VARIABLE > 15
        #define BIG_VARIABLE 1
    // Wrong
    #if MY_VARIABLE > 10
    #if MY_OTHER_VARIABLE > 15
    #define BIG_VARIABLE 1
  3. Public PETSc include files, petsc*.h, should not reference private PETSc petsc/private/*impl.h include files.

  4. Public and private PETSc include files cannot reference include files located in the PETSc source tree.

  5. All public functions must sanity-check their arguments using the appropriate PetscValidXXX() macros. These must appear between PetscFunctionBegin and PetscFunctionReturn() For example

    PetscErrorCode PetscPublicFunction(Vec v, PetscScalar *array, PetscInt collectiveInt)

    See include/petsc/private/petscimpl.h and search for “PetscValid” to see all available checker macros.

  6. When possible, use PetscDefined() instead of preprocessor conditionals. For example use:

    if (PetscDefined(USE_DEBUG)) { ... }

    instead of:

    #if defined(PETSC_USE_DEBUG)

    The former usage allows syntax and type checking in all configurations of PETSc, where as the latter needs to be compiled with and without debugging just to confirm that it compiles.

  7. The first line of the executable statements in functions must be PetscFunctionBegin;

  8. Use PetscFunctionReturn(returnvalue), not return(returnvalue);

  9. Never put a function call in a return statement; do not write

    PetscFunctionReturn( somefunction(...) ); /* Incorrect */
  10. Do not put a blank line immediately after PetscFunctionBegin; or a blank line immediately before PetscFunctionReturn(0);.

  11. Do not use sqrt(), pow(), sin(), and so on directly in PETSc C/C++ source code or examples (usage is fine in Fortran source code). Rather, use PetscSqrtScalar(), PetscSqrtReal(), and so on, depending on the context. See petscmath.h for expressions to use.

  12. Do not include assert.h in PETSc source code. Do not use assert(), it doesn’t play well in the parallel MPI world. You may use PetscAssert() where appropriate.

  13. Try to make error messages short but informative. The user should be able to reasonably diagnose the greater problem from your error message.

  14. Except in code that may be called before PETSc is fully initialized, always use PetscMallocN() (for example, PetscMalloc1()), PetscCallocN(), PetscNew(), and PetscFree(), not malloc() and free().

  15. MPI routines and macros that are not part of the 2.1 standard should not be used in PETSc without appropriate configure checks and #if PetscDefined() checks. Code should also be provided that works if the MPI feature is not available, for example,

    #if PetscDefined(HAVE_MPI_REDUCE_LOCAL)
      ierr = MPI_Reduce_local(inbuf,inoutbuf,count,MPIU_INT,MPI_SUM);CHKERRMPI(ierr);
      ierr = MPI_Reduce(inbuf,inoutbuf,count,MPIU_INT,
  16. Do not introduce PETSc routines that provide essentially the same functionality as an available MPI routine. For example, do not write a routine PetscGlobalSum() that takes a scalar value and performs an MPI_Allreduce() on it. Instead, use the MPI routine MPI_Allreduce() directly in the code.

  17. Never use a local variable counter such as PetscInt flops = 0; to accumulate flops and then call PetscLogFlops(); always just call PetscLogFlops() directly when needed.

  18. Library symbols meant to be directly usable by the user should be declared PETSC_EXTERN in their respective public header-file. Symbols intended to be for internal use only should instead be declared PETSC_INTERN. Note that doing so is not necessary in the case of symbols local to a single translation unit, these should be declared static. Note that PETSc can be configured to build a separate shared library for each top-level class (Mat, Vec, KSP, and so on) and that plugin implementations of these classes can be included as separate shared libraries; thus, otherwise private symbols may need to be marked PETSC_SINGLE_LIBRARY_INTERN. For example

    • MatStashCreate_Private() is marked PETSC_INTERN as it is used across compilation units, but only within the Mat package;

    • all functions, such as KSPCreate(), included in the public headers (include/petsc*.h) should be marked PETSC_EXTERN;

    • PetscDeviceInitializeDefaultDevice_Internal() is marked PETSC_SINGLE_LIBRARY_INTERN as it may be used across library boundaries, but is not intended to be visible to users;

  19. Before removing or renaming an API function, type, or enumerator, PETSC_DEPRECATED_XXX() should be used in the relevant header file to indicate the new, correct usage and the version number where the deprecation will first appear. The old function or type, with the deprecation warning, should remain for at least one major release. The function or type’s manual page should be updated (see Manual Page Format). For example,

    typedef NewType OldType PETSC_DEPRECATED_TYPEDEF("Use NewType (since version 3.9)");
    PETSC_DEPRECATED_FUNCTION("Use NewFunction() (since version 3.9)") PetscErrorCode OldFunction();
    typedef enum {
    } MyEnum;

    Note that after compiler preprocessing, the enum above would be transformed to something like

    typedef enum {
      OLD_ENUMERATOR __attribute((deprecated)) = 3,
    } MyEnum;
  20. Before removing or renaming an options database key, PetscOptionsDeprecated() should be used for at least one major release.

  21. The format strings in PETSc ASCII output routines, such as PetscPrintf, take a %" PetscInt_FMT " for all PETSc variables of type PetscInt, not a %d.

  22. All arguments of type PetscReal to PETSc ASCII output routines, such as PetscPrintf, must be cast to double, for example,

    PetscPrintf(PETSC_COMM_WORLD,"Norm %g\n",(double)norm);

Formatted Comments#

PETSc uses formatted comments and the Sowing packages [Gro95b] [Gro95a] to generate documentation (manual pages) and the Fortran interfaces. Documentation for Sowing and the formatting may be found at; in particular, see the documentation for doctext.

  • /*@
    a formatted comment of a function that will be used for both documentation and a Fortran interface.
  • /*@C
    a formatted comment of a function that will be used only for documentation, not to generate a Fortran interface. In general, such labeled C functions should have a custom Fortran interface provided. Functions that take char* or function pointer arguments must have the C symbol and a custom Fortran interface provided.
  • /*E
    a formatted comment of an enum used for documentation only. Note that each of these needs to be listed in lib/petsc/conf/bfort-petsc.txt as a native and defined in the corresponding include/petsc/finclude/petscxxx.h Fortran include file and the values set as parameters in the file src/SECTION/f90-mod/petscSUBSECTION.h, for example, src/vec/f90-mod/petscis.h.
  • /*S
    a formatted comment for a data type such as KSP. Note that each of these needs to be listed in lib/petsc/conf/bfort-petsc.txt as a nativeptr.
  • /*MC
    a formatted comment of a CPP macro or enum value for documentation.

The Fortran interface files supplied manually by developer go into the two directories ftn-custom and f90-custom, while those generated by Sowing go into ftn-auto.

Manual Page Format#

Each function, typedef, class, macro, enum, and so on in the public API should include the following data, correctly formatted (see codes section) to generate complete manual pages and Fortran interfaces with Sowing. All entries below should be separated by blank lines. Except where noted, add a newline after the section headings.

  1. The item’s name, followed by a dash and brief (one-sentence) description.

  2. If documenting a function implemented with a preprocessor macro (e.g., PetscOptionsBegin()), an explicit Synopsis: section noting the required header and the function signature.

  3. If documenting a function, a description of the function’s “collectivity” (whether all ranks in an MPI communicator need to participate). Unless otherwise noted, it’s assumed that this collectivity is with respect to the MPI communicator associated with the first argument.

    • Not Collective if the function need not be called on all MPI ranks

    • Collective [on XXX] if the function is a collective operation (with respect to the MPI communicator associated with argument XXX)

    • Logically Collective [on XXX][; YYY must contain common value] if the function is collective but does not require any actual synchronization (e.g. setting class parameters uniformly). Any argument YYY which must have the same value on all ranks of the MPI communicator should be noted here.

  4. If documenting a function with input parameters, a list of input parameter descriptions in an Input Parameter(s): section.

  5. If documenting a function with output parameters, a list of output parameter descriptions in an Output Parameter(s): section.

  6. If documenting a function that interacts with the options database, a list of options database keys in an Options Database Key(s): section.

  7. (Optional) a Notes: section containing in-depth discussion, technical caveats, special cases, and so on. If it is ambiguous whether returned pointers/objects need to be freed/destroyed by the user or not, this information should be mentioned here.

  8. (If applicable) a Fortran Notes: section detailing any relevant differences in calling or using the item from Fortran.

  9. (If applicable) a Developer Notes: section detailing any relevant information about the code for developers, for example, why a particular algorithm was implemented.

  10. Level: (no newline) followed by beginner, intermediate, advanced, developer, or deprecated.

  11. .seealso: (no newline), followed by a list of related manual pages. These manual pages should usually also point back to this manual page in their seealso: sections.


Type also refers to the string name of the subclass.

Spelling and Capitalization#

  1. Proper nouns, including Unix, Linux, X Windows, and Microsoft Windows should be capitalized. This includes all operating systems.

  2. Company names and product names should be capitalized.

  3. Company names and terms that are traditionally all capitalized, for example, NVIDIA and CUDA should be all capitalized.

  4. Unix should not be all capitalized.

  5. Microsoft Windows should always be written out with two words. That is it should not be shortened to Windows.

  6. CMake should be capitalized as shown.



W Gropp. Users manual for doctext: producing documentation from source code. Technical Report ANL/MCS-TM-206, Argonne National Laboratory, 1995.


W Gropp. Users manual for bfort: producing Fortran interfaces to C source code. Technical Report ANL/MCS-TM-208, Argonne National Laboratory, 1995.