File: compiler-pickyness.rst

package info (click to toggle)
openmpi 5.0.8-4
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 201,684 kB
  • sloc: ansic: 613,078; makefile: 42,353; sh: 11,194; javascript: 9,244; f90: 7,052; java: 6,404; perl: 5,179; python: 1,859; lex: 740; fortran: 61; cpp: 20; tcl: 12
file content (29 lines) | stat: -rw-r--r-- 1,240 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Compiler Pickyness by Default
=============================

If you are building Open MPI from a Git clone (i.e., there is a
``.git`` directory in your build tree), the default build includes
extra compiler pickyness, which will result in more compiler warnings
than in non-developer builds.  Getting these extra compiler warnings
is helpful to Open MPI developers in making the code base as clean as
possible.

Developers can disable this picky-by-default behavior by using the
``--disable-picky`` configure option.  Also note that extra-picky
compiles do *not* happen automatically when you do a VPATH build
(e.g., if ``.git`` is in your source tree, but not in your build
tree).

Prior versions of Open MPI would automatically activate a lot of
(performance-reducing) debugging code by default if ``.git`` was found
in your build tree.  This is no longer true.  You can manually enable
these (performance-reducing) debugging features in the Open MPI code
base with these configure options:

* ``--enable-debug``
* ``--enable-mem-debug``
* ``--enable-mem-profile``

.. note:: These options are really only relevant to those who are
   developing Open MPI itself.  They are not generally helpful for
   debugging general MPI applications.