[docs] [NFC] Removed excess spacing

[abrachet]

Summary

Removed excess new lines from documentations. As far as I can tell, it seems as though restructured text is agnostic to new lines, the use of new lines was inconsistent and had no effect on how the files were being displayed.

[jhenderson]

LGTM. Have you built the docs? It would be interesting comparing the html output before and after this change, before this goes in, to make sure that there is indeed no difference.

llvm/docs/CommandGuide/bugpoint.rst

 
 **--load** *plugin*
 
  Load the dynamic object *plugin* into **bugpoint** itself.  This object should
  register new optimization passes.  Once loaded, the object will add new command
  line options to enable various optimizations.  To see the new complete list of
  optimizations, use the **-help** and **--load** options together; for example:
 
-
  .. code-block:: bash
 
       bugpoint --load myNewPass.so -help
 
 **--mlimit** *megabytes*
 
  Specifies an upper limit on memory usage of the optimization and codegen. Set
  to zero to disable the limit.

llvm/docs/CommandGuide/dsymutil.rst

  Dump the *executable*'s debug-map (the list of the object files containing the
  debug information) in YAML format and exit. Not DWARF link will take place.
 
 .. option:: -f, --flat
 
  Produce a flat dSYM file. A ``.dwarf`` extension will be appended to the
  executable name unless the output file is specified using the -o option.
 
-
 .. option:: -z, --minimize
 
  When used when creating a dSYM file, this option will suppress the emission of
  the .debug_inlines, .debug_pubnames, and .debug_pubtypes sections since
  dsymutil currently has better equivalents: .apple_names and .apple_types. When
  used in conjunction with --update option, this option will cause redundant
  accelerator tables to be removed.
 

llvm/docs/CommandGuide/llc.rst

 
 If :program:`llc` succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.
 
 SEE ALSO
 --------
 
 lli
-

llvm/docs/CommandGuide/llvm-ar.rst

 llvm-ar - LLVM archiver
 =======================
 
 .. program:: llvm-ar
 
 SYNOPSIS
 --------
 
-
 **llvm-ar** [-]{dmpqrtx}[Rabfikou] [relpos] [count] <archive> [files...]
 
-
 DESCRIPTION
 -----------
 
-
 The **llvm-ar** command is similar to the common Unix utility, ``ar``. It
 archives several files together into a single file. The intent for this is
 to produce archive libraries by LLVM bitcode that can be linked into an
 LLVM program. However, the archive can contain any kind of file. By default,
 **llvm-ar** generates a symbol table that makes linking faster because
 only the symbol table needs to be consulted, not each individual file member
 of the archive.
 
 The **llvm-ar** command can be used to *read* SVR4, GNU and BSD style archive
 files. However, right now it can only write in the GNU format. If an
 SVR4 or BSD style archive is used with the ``r`` (replace) or ``q`` (quick
 update) operations, the archive will be reconstructed in GNU format.
 
 Here's where **llvm-ar** departs from previous ``ar`` implementations:
 
-
 *Symbol Table*
 
  Since **llvm-ar** supports bitcode files. The symbol table it creates
  is in GNU format and includes both native and bitcode files.
 
-
 *Long Paths*
 
  Currently **llvm-ar** can read GNU and BSD long file names, but only writes
  archives with the GNU format.
 
-
-
 OPTIONS
 -------
 
-
 The options to **llvm-ar** are compatible with other ``ar`` implementations.
 However, there are a few modifiers (*R*) that are not found in other ``ar``
 implementations. The options to **llvm-ar** specify a single basic operation to
 perform on the archive, a variety of modifiers for that operation, the name of
 the archive file, and an optional list of file names. These options are used to
 determine how **llvm-ar** should process the archive file.
 
 The Operations and Modifiers are explained in the sections below. The minimal
 set of options is at least one operator and the name of the archive. Typically
 archive files end with a ``.a`` suffix, but this is not required. Following
 the *archive-name* comes a list of *files* that indicate the specific members
 of the archive to operate on. If the *files* option is not specified, it
 generally means either "none" or "all" members, depending on the operation.
 
 Operations
 ~~~~~~~~~~
 
-
-
 d
 
  Delete files from the archive. No modifiers are applicable to this operation.
  The *files* options specify which members should be removed from the
  archive. It is not an error if a specified file does not appear in the archive.
  If no *files* are specified, the archive is not modified.
 
-
-
 m[abi]
 
  Move files from one location in the archive to another. The *a*, *b*, and
  *i* modifiers apply to this operation. The *files* will all be moved
  to the location given by the modifiers. If no modifiers are used, the files
  will be moved to the end of the archive. If no *files* are specified, the
  archive is not modified.
 
-
-
 p
 
  Print files to the standard output. This operation simply prints the
  *files* indicated to the standard output. If no *files* are
  specified, the entire  archive is printed.  Printing bitcode files is
  ill-advised as they might confuse your terminal settings. The *p*
  operation never modifies the archive.
 
-
-
 q
 
  Quickly append files to the end of the archive.  This operation quickly adds the
  *files* to the archive without checking for duplicates that should be
  removed first. If no *files* are specified, the archive is not modified.
  Because of the way that **llvm-ar** constructs the archive file, its dubious
  whether the *q* operation is any faster than the *r* operation.
 
-
-
 r[abu]
 
  Replace or insert file members. The *a*, *b*,  and *u*
  modifiers apply to this operation. This operation will replace existing
  *files* or insert them at the end of the archive if they do not exist. If no
  *files* are specified, the archive is not modified.
 
-
-
 t[v]
 
  Print the table of contents. Without any modifiers, this operation just prints
  the names of the members to the standard output. With the *v* modifier,
  **llvm-ar** also prints out the file type (B=bitcode, S=symbol
  table, blank=regular file), the permission mode, the owner and group, the
  size, and the date. If any *files* are specified, the listing is only for
  those files. If no *files* are specified, the table of contents for the
  whole archive is printed.
 
-
-
 x[oP]
 
  Extract archive members back to files. The *o* modifier applies to this
  operation. This operation retrieves the indicated *files* from the archive
  and writes them back to the operating system's file system. If no
  *files* are specified, the entire archive is extract.
 
-
-
-
 Modifiers (operation specific)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-
 The modifiers below are specific to certain operations. See the Operations
 section (above) to determine which modifiers are applicable to which operations.
 
-
 [a]
 
  When inserting or moving member files, this option specifies the destination of
  the new files as being after the *relpos* member. If *relpos* is not found,
  the files are placed at the end of the archive.
 
-
-
 [b]
 
  When inserting or moving member files, this option specifies the destination of
  the new files as being before the *relpos* member. If *relpos* is not
  found, the files are placed at the end of the archive. This modifier is
  identical to the *i* modifier.
 
-
-
 [i]
 
  A synonym for the *b* option.
 
-
-
 [o]
 
  When extracting files, this option will cause **llvm-ar** to preserve the
  original modification times of the files it writes.
 
-
-
 [u]
 
  When replacing existing files in the archive, only replace those files that have
  a time stamp than the time stamp of the member in the archive.
 
-
-
-
 Modifiers (generic)
 ~~~~~~~~~~~~~~~~~~~
 
-
 The modifiers below may be applied to any operation.
 
-
 [c]
 
  For all operations, **llvm-ar** will always create the archive if it doesn't
  exist. Normally, **llvm-ar** will print a warning message indicating that the
  archive is being created. Using this modifier turns off that warning.
 
 
-
 [s]
 
  This modifier requests that an archive index (or symbol table) be added to the
  archive. This is the default mode of operation. The symbol table will contain
  all the externally visible functions and global variables defined by all the
  bitcode files in the archive.
 
-
-
 [S]
 
  This modifier is the opposite of the *s* modifier. It instructs **llvm-ar** to
  not build the symbol table. If both *s* and *S* are used, the last modifier to
  occur in the options will prevail.
 
-
-
 [v]
 
  This modifier instructs **llvm-ar** to be verbose about what it is doing. Each
  editing operation taken against the archive will produce a line of output saying
  what is being done.
 
-
-
-
-
 STANDARDS
 ---------
 
-
 The **llvm-ar** utility is intended to provide a superset of the IEEE Std 1003.2
 (POSIX.2) functionality for ``ar``. **llvm-ar** can read both SVR4 and BSD4.4 (or
 macOS) archives. If the ``f`` modifier is given to the ``x`` or ``r`` operations
 then **llvm-ar** will write SVR4 compatible archives. Without this modifier,
 **llvm-ar** will write BSD4.4 compatible archives that have long names
 immediately after the header and indicated using the "#1/ddd" notation for the
 name in the header.
 
-
 FILE FORMAT
 -----------
 
-
 The file format for LLVM Archive files is similar to that of BSD 4.4 or macOS
 archive files. In fact, except for the symbol table, the ``ar`` commands on those
 operating systems should be able to read LLVM archive files. The details of the
 file format follow.
 
 Each archive begins with the archive magic number which is the eight printable
 characters "!<arch>\n" where \n represents the newline character (0x0A).
 Following the magic number, the file is composed of even length members that
 begin with an archive header and end with a \n padding character if necessary
 (to make the length even). Each file member is composed of a header (defined
 below), an optional newline-terminated "long file name" and the contents of
 the file.
 
 The fields of the header are described in the items below. All fields of the
 header contain only ASCII characters, are left justified and are right padded
 with space characters.
 
-
 name - char[16]
 
  This field of the header provides the name of the archive member. If the name is
  longer than 15 characters or contains a slash (/) character, then this field
  contains ``#1/nnn`` where ``nnn`` provides the length of the name and the ``#1/``
  is literal.  In this case, the actual name of the file is provided in the ``nnn``
  bytes immediately following the header. If the name is 15 characters or less, it
  is contained directly in this field and terminated with a slash (/) character.
 
-
-
 date - char[12]
 
  This field provides the date of modification of the file in the form of a
  decimal encoded number that provides the number of seconds since the epoch
  (since 00:00:00 Jan 1, 1970) per Posix specifications.
 
-
-
 uid - char[6]
 
  This field provides the user id of the file encoded as a decimal ASCII string.
  This field might not make much sense on non-Unix systems. On Unix, it is the
  same value as the st_uid field of the stat structure returned by the stat(2)
  operating system call.
 
-
-
 gid - char[6]
 
  This field provides the group id of the file encoded as a decimal ASCII string.
  This field might not make much sense on non-Unix systems. On Unix, it is the
  same value as the st_gid field of the stat structure returned by the stat(2)
  operating system call.
 
-
-
 mode - char[8]
 
  This field provides the access mode of the file encoded as an octal ASCII
  string. This field might not make much sense on non-Unix systems. On Unix, it
  is the same value as the st_mode field of the stat structure returned by the
  stat(2) operating system call.
 
-
-
 size - char[10]
 
  This field provides the size of the file, in bytes, encoded as a decimal ASCII
  string.
 
-
-
 fmag - char[2]
 
  This field is the archive file member magic number. Its content is always the
  two characters back tick (0x60) and newline (0x0A). This provides some measure
  utility in identifying archive files that have been corrupted.
 
-
 offset - vbr encoded 32-bit integer
 
  The offset item provides the offset into the archive file where the bitcode
  member is stored that is associated with the symbol. The offset value is 0
  based at the start of the first "normal" file member. To derive the actual
  file offset of the member, you must add the number of bytes occupied by the file
  signature (8 bytes) and the symbol tables. The value of this item is encoded
  using variable bit rate encoding to reduce the size of the symbol table.
  Variable bit rate encoding uses the high bit (0x80) of each byte to indicate
  if there are more bytes to follow. The remaining 7 bits in each byte carry bits
  from the value. The final byte does not have the high bit set.
 
-
-
 length - vbr encoded 32-bit integer
 
  The length item provides the length of the symbol that follows. Like this
  *offset* item, the length is variable bit rate encoded.
 
-
-
 symbol - character array
 
  The symbol item provides the text of the symbol that is associated with the
  *offset*. The symbol is not terminated by any character. Its length is provided
  by the *length* field. Note that is allowed (but unwise) to use non-printing
  characters (even 0x00) in the symbol. This allows for multiple encodings of
  symbol names.
 
-
-
-
 EXIT STATUS
 -----------
 
-
 If **llvm-ar** succeeds, it will exit with 0.  A usage error, results
 in an exit code of 1. A hard (file system typically) error results in an
 exit code of 2. Miscellaneous or unknown errors result in an
 exit code of 3.
 
-
 SEE ALSO
 --------
 
-
 ar(1)

llvm/docs/CommandGuide/llvm-bcanalyzer.rst

 
  The total number of bytes saved in this function by using the Variable Bit
  Rate encoding scheme.  The percentage is relative to # of VBR Expanded Bytes.
 
 SEE ALSO
 --------
 
 :doc:`/CommandGuide/llvm-dis`, :doc:`/BitCodeFormat`
-

llvm/docs/CommandGuide/llvm-build.rst

 llvm-build - LLVM Project Build Utility
 =======================================
 
 .. program:: llvm-build
 
 SYNOPSIS
 --------
 
-
 **llvm-build** [*options*]
 
-
 DESCRIPTION
 -----------
 
-
 **llvm-build** is a tool for working with LLVM projects that use the LLVMBuild
 system for describing their components.
 
 At heart, **llvm-build** is responsible for loading, verifying, and manipulating
 the project's component data. The tool is primarily designed for use in
 implementing build systems and tools which need access to the project structure
 information.
 
-
 OPTIONS
 -------
 
-
-
 **-h**, **--help**
 
  Print the builtin program help.
 
-
-
 **--source-root**\ =\ *PATH*
 
  If given, load the project at the given source root path. If this option is not
  given, the location of the project sources will be inferred from the location of
  the **llvm-build** script itself.
 
-
-
 **--print-tree**
 
  Print the component tree for the project.
 
-
-
 **--write-library-table**
 
  Write out the C++ fragment which defines the components, library names, and
  required libraries. This C++ fragment is built into llvm-config|llvm-config
  in order to provide clients with the list of required libraries for arbitrary
  component combinations.
 
-
-
 **--write-llvmbuild**
 
  Write out new *LLVMBuild.txt* files based on the loaded components. This is
  useful for auto-upgrading the schema of the files. **llvm-build** will try to a
  limited extent to preserve the comments which were written in the original
  source file, although at this time it only preserves block comments that precede
  the section names in the *LLVMBuild* files.
 
-
-
 **--write-cmake-fragment**
 
  Write out the LLVMBuild in the form of a CMake fragment, so it can easily be
  consumed by the CMake based build system. The exact contents and format of this
  file are closely tied to how LLVMBuild is integrated with CMake, see LLVM's
  top-level CMakeLists.txt.
 
-
-
 **--write-make-fragment**
 
  Write out the LLVMBuild in the form of a Makefile fragment, so it can easily be
  consumed by a Make based build system. The exact contents and format of this
  file are closely tied to how LLVMBuild is integrated with the Makefiles, see
  LLVM's Makefile.rules.
 
-
-
 **--llvmbuild-source-root**\ =\ *PATH*
 
  If given, expect the *LLVMBuild* files for the project to be rooted at the
  given path, instead of inside the source tree itself. This option is primarily
  designed for use in conjunction with **--write-llvmbuild** to test changes to
  *LLVMBuild* schema.
 
-
-
-
 EXIT STATUS
 -----------
 
-
 **llvm-build** exits with 0 if operation was successful. Otherwise, it will exist
 with a non-zero value.

llvm/docs/CommandGuide/llvm-config.rst

 llvm-config - Print LLVM compilation options
 ============================================
 
 .. program:: llvm-config
 
 SYNOPSIS
 --------
 
-
 **llvm-config** *option* [*components*...]
 
-
 DESCRIPTION
 -----------
 
-
 **llvm-config** makes it easier to build applications that use LLVM.  It can
 print the compiler flags, linker flags and object libraries needed to link
 against LLVM.
 
-
 EXAMPLES
 --------
 
-
 To link against the JIT:
 
-
 .. code-block:: sh
 
    g++ `llvm-config --cxxflags` -o HowToUseJIT.o -c HowToUseJIT.cpp
    g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o \
        `llvm-config --libs engine bcreader scalaropts`
 
-
-
 OPTIONS
 -------
 
-
-
 **--version**
 
  Print the version number of LLVM.
 
-
-
 **-help**
 
  Print a summary of **llvm-config** arguments.
 
-
-
 **--prefix**
 
  Print the installation prefix for LLVM.
 
-
-
 **--src-root**
 
  Print the source root from which LLVM was built.
 
-
-
 **--obj-root**
 
  Print the object root used to build LLVM.
 
-
-
 **--bindir**
 
  Print the installation directory for LLVM binaries.
 
-
-
 **--includedir**
 
  Print the installation directory for LLVM headers.
 
-
-
 **--libdir**
 
  Print the installation directory for LLVM libraries.
 
-
-
 **--cxxflags**
 
  Print the C++ compiler flags needed to use LLVM headers.
 
-
-
 **--ldflags**
 
  Print the flags needed to link against LLVM libraries.
 
-
-
 **--libs**
 
  Print all the libraries needed to link against the specified LLVM
  *components*, including any dependencies.
 
-
-
 **--libnames**
 
  Similar to **--libs**, but prints the bare filenames of the libraries
  without **-l** or pathnames.  Useful for linking against a not-yet-installed
  copy of LLVM.
 
-
-
 **--libfiles**
 
  Similar to **--libs**, but print the full path to each library file.  This is
  useful when creating makefile dependencies, to ensure that a tool is relinked if
  any library it uses changes.
 
-
-
 **--components**
 
  Print all valid component names.
 
-
-
 **--targets-built**
 
  Print the component names for all targets supported by this copy of LLVM.
 
-
-
 **--build-mode**
 
  Print the build mode used when LLVM was built (e.g. Debug or Release)
 
 
-
-
 COMPONENTS
 ----------
 
-
 To print a list of all available components, run **llvm-config
 --components**.  In most cases, components correspond directly to LLVM
 libraries.  Useful "virtual" components include:
 
-
 **all**
 
  Includes all LLVM libraries.  The default if no components are specified.
 
-
-
 **backend**
 
  Includes either a native backend or the C backend.
 
-
-
 **engine**
 
  Includes either a native JIT or the bitcode interpreter.
 
 
-
-
 EXIT STATUS
 -----------
 
-
 If **llvm-config** succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.

llvm/docs/CommandGuide/llvm-cov.rst

  file name will be suffixed by ``##`` followed by MD5 hash calculated for it.
 
 EXIT STATUS
 ^^^^^^^^^^^
 
 :program:`llvm-cov gcov` returns 1 if it cannot read input files.  Otherwise,
 it exits with zero.
 
-
 .. program:: llvm-cov show
 
 .. _llvm-cov-show:
 
 SHOW COMMAND
 ------------
 
 SYNOPSIS

llvm/docs/CommandGuide/llvm-diff.rst

 llvm-diff - LLVM structural 'diff'
 ==================================
 
 .. program:: llvm-diff
 
 SYNOPSIS
 --------
 
-
 **llvm-diff** [*options*] *module 1* *module 2* [*global name ...*]
 
-
 DESCRIPTION
 -----------
 
-
 **llvm-diff** compares the structure of two LLVM modules, primarily
 focusing on differences in function definitions.  Insignificant
 differences, such as changes in the ordering of globals or in the
 names of local values, are ignored.
 
 An input module will be interpreted as an assembly file if its name
 ends in '.ll';  otherwise it will be read in as a bitcode file.
 
 If a list of global names is given, just the values with those names
 are compared; otherwise, all global values are compared, and
 diagnostics are produced for globals which only appear in one module
 or the other.
 
 **llvm-diff** compares two functions by comparing their basic blocks,
 beginning with the entry blocks.  If the terminators seem to match,
 then the corresponding successors are compared; otherwise they are
 ignored.  This algorithm is very sensitive to changes in control flow,
 which tend to stop any downstream changes from being detected.
 
 **llvm-diff** is intended as a debugging tool for writers of LLVM
 passes and frontends.  It does not have a stable output format.
 
-
 EXIT STATUS
 -----------
 
-
 If **llvm-diff** finds no differences between the modules, it will exit
 with 0 and produce no output.  Otherwise it will exit with a non-zero
 value.
 
-
 BUGS
 ----
 
-
 Many important differences, like changes in linkage or function
 attributes, are not diagnosed.
 
 Changes in memory behavior (for example, coalescing loads) can cause
 massive detected differences in blocks.

llvm/docs/CommandGuide/llvm-dis.rst

 llvm-dis - LLVM disassembler
 ============================
 
 .. program:: llvm-dis
 
 SYNOPSIS
 --------
 
-
 **llvm-dis** [*options*] [*filename*]
 
-
 DESCRIPTION
 -----------
 
-
 The **llvm-dis** command is the LLVM disassembler.  It takes an LLVM
 bitcode file and converts it into human-readable LLVM assembly language.
 
 If filename is omitted or specified as ``-``, **llvm-dis** reads its
 input from standard input.
 
 If the input is being read from standard input, then **llvm-dis**
 will send its output to standard output by default.  Otherwise, the
 output will be written to a file named after the input file, with
 a ``.ll`` suffix added (any existing ``.bc`` suffix will first be
 removed).  You can override the choice of output file using the
 **-o** option.
 
-
 OPTIONS
 -------
 
-
-
 **-f**
 
  Enable binary output on terminals.  Normally, **llvm-dis** will refuse to
  write raw bitcode output if the output stream is a terminal. With this option,
  **llvm-dis** will write raw bitcode regardless of the output device.
 
-
-
 **-help**
 
  Print a summary of command line options.
 
-
-
 **-o** *filename*
 
  Specify the output file name.  If *filename* is -, then the output is sent
  to standard output.
 
-
-
-
 EXIT STATUS
 -----------
 
-
 If **llvm-dis** succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.
 
-
 SEE ALSO
 --------
 
-
 llvm-as|llvm-as

llvm/docs/CommandGuide/llvm-exegesis.rst

 
 .. image:: llvm-exegesis-analysis.png
   :align: center
 
 Note that the scheduling class names will be resolved only when
 :program:`llvm-exegesis` is compiled in debug mode, else only the class id will
 be shown. This does not invalidate any of the analysis results though.
 
-
 OPTIONS
 -------
 
 .. option:: -help
 
  Print a summary of command line options.
 
 .. option:: -opcode-index=<LLVM opcode index>

llvm/docs/CommandGuide/llvm-extract.rst

 
 If :program:`llvm-extract` succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.
 
 SEE ALSO
 --------
 
 bugpoint
-

llvm/docs/CommandGuide/llvm-lib.rst

 llvm-lib - LLVM lib.exe compatible library tool
 ===============================================
 
 .. program:: llvm-lib
 
 SYNOPSIS
 --------
 
-
 **llvm-lib** [/libpath:<path>] [/out:<output>] [/llvmlibthin]
 [/ignore] [/machine] [/nologo] [files...]
 
-
 DESCRIPTION
 -----------
 
-
 The **llvm-lib** command is intended to be a ``lib.exe`` compatible
 tool. See https://msdn.microsoft.com/en-us/library/7ykb2k5f for the
 general description.
 
 **llvm-lib** has the following extensions:
 
 * Bitcode files in symbol tables.
   **llvm-lib** includes symbols from both bitcode files and regular
   object files in the symbol table.
 
 * Creating thin archives.
   The /llvmlibthin option causes **llvm-lib** to create thin archive
   that contain only the symbol table and the header for the various
   members. These files are much smaller, but are not compatible with
   link.exe (lld can handle them).

llvm/docs/CommandGuide/llvm-link.rst

  This typically includes a message for each bitcode file linked in and for each
  library found.
 
 EXIT STATUS
 -----------
 
 If :program:`llvm-link` succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.
-
-

llvm/docs/CommandGuide/llvm-profdata.rst

 
 The result overlap distribution is a percentage number, ranging from 0.0% to
 100.0%, where 0.0% means there is no overlap and 100.0% means a perfect
 overlap.
 
 Here is an example, if *base profile file* has counts of {400, 600}, and
 *test profile file* has matched counts of {60000, 40000}. The *overlap* is 80%.
 
-
 OPTIONS
 ^^^^^^^
 
 .. option:: -function=string
 
  Print details for a function if the function's name contains the given string.
 
 .. option:: -help

llvm/docs/CommandGuide/llvm-stress.rst

 .. option:: -seed seed
 
  Specify the seed to be used for the randomly generated instructions.
 
 EXIT STATUS
 -----------
 
 :program:`llvm-stress` returns 0.
-

llvm/docs/CommandGuide/opt.rst

 
  Print module after each transformation.
 
 EXIT STATUS
 -----------
 
 If :program:`opt` succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.
-