[docs] [NFC] Removed excess spacing

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.

Reviewers: jhenderson, rupprecht, JDevlieghere

Reviewed By: jhenderson

Subscribers: llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D63971

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@365105 91177308-0d34-0410-b5e6-96231b3b80d8

docs/CommandGuide/bugpoint.rst

@@ -109,7 +109,6 @@ OPTIONS
  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

docs/CommandGuide/dsymutil.rst

@@ -37,7 +37,6 @@ OPTIONS
  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

docs/CommandGuide/llc.rst

@@ -212,4 +212,3 @@ SEE ALSO
 --------
 
 lli
-

docs/CommandGuide/llvm-ar.rst

@@ -6,14 +6,11 @@ llvm-ar - LLVM archiver
 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
@@ -29,24 +26,19 @@ 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
@@ -64,8 +56,6 @@ 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.
@@ -73,8 +63,6 @@ d
  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
@@ -83,8 +71,6 @@ m[abi]
  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
@@ -93,8 +79,6 @@ p
  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
@@ -103,8 +87,6 @@ q
  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*
@@ -112,8 +94,6 @@ r[abu]
  *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
@@ -124,8 +104,6 @@ t[v]
  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
@@ -133,25 +111,18 @@ x[oP]
  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
@@ -159,36 +130,25 @@ section (above) to determine which modifiers are applicable to which operations.
  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
@@ -196,7 +156,6 @@ The modifiers below may be applied to any operation.
  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
@@ -204,30 +163,21 @@ The modifiers below may be applied to any operation.
  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
@@ -236,11 +186,9 @@ then **llvm-ar** will write SVR4 compatible archives. Without this modifier,
 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
@@ -258,7 +206,6 @@ 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
@@ -268,16 +215,12 @@ name - char[16]
  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.
@@ -285,8 +228,6 @@ uid - char[6]
  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.
@@ -294,8 +235,6 @@ gid - char[6]
  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
@@ -303,22 +242,17 @@ mode - char[8]
  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
@@ -331,15 +265,11 @@ offset - vbr encoded 32-bit integer
  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
@@ -348,21 +278,15 @@ symbol - character array
  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)

docs/CommandGuide/llvm-bcanalyzer.rst

@@ -304,4 +304,3 @@ SEE ALSO
 --------
 
 :doc:`/CommandGuide/llvm-dis`, :doc:`/BitCodeFormat`
-

docs/CommandGuide/llvm-build.rst

@@ -6,14 +6,11 @@ llvm-build - LLVM Project Build Utility
 SYNOPSIS
 --------
 
-
 **llvm-build** [*options*]
 
-
 DESCRIPTION
 -----------
 
-
 **llvm-build** is a tool for working with LLVM projects that use the LLVMBuild
 system for describing their components.
 
@@ -22,32 +19,23 @@ 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
@@ -55,8 +43,6 @@ OPTIONS
  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
@@ -65,8 +51,6 @@ OPTIONS
  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
@@ -74,8 +58,6 @@ OPTIONS
  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
@@ -83,8 +65,6 @@ OPTIONS
  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
@@ -92,12 +72,8 @@ OPTIONS
  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.

docs/CommandGuide/llvm-config.rst

@@ -6,172 +6,121 @@ llvm-config - Print LLVM compilation options
 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.

docs/CommandGuide/llvm-cov.rst

@@ -163,7 +163,6 @@ 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:

docs/CommandGuide/llvm-diff.rst

@@ -6,14 +6,11 @@ llvm-diff - LLVM structural '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
@@ -36,20 +33,16 @@ 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.
 

docs/CommandGuide/llvm-dis.rst

@@ -6,14 +6,11 @@ llvm-dis - LLVM disassembler
 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.
 
@@ -27,44 +24,31 @@ 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

docs/CommandGuide/llvm-exegesis.rst

@@ -166,7 +166,6 @@ 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
 -------
 

docs/CommandGuide/llvm-extract.rst

@@ -78,4 +78,3 @@ SEE ALSO
 --------
 
 bugpoint
-

docs/CommandGuide/llvm-lib.rst

@@ -6,15 +6,12 @@ llvm-lib - LLVM lib.exe compatible library tool
 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.

docs/CommandGuide/llvm-link.rst

@@ -54,5 +54,3 @@ 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.
-
-

docs/CommandGuide/llvm-profdata.rst

@@ -273,7 +273,6 @@ 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
 ^^^^^^^
 

docs/CommandGuide/llvm-stress.rst

@@ -33,4 +33,3 @@ EXIT STATUS
 -----------
 
 :program:`llvm-stress` returns 0.
-

docs/CommandGuide/opt.rst

@@ -122,4 +122,3 @@ EXIT STATUS
 
 If :program:`opt` succeeds, it will exit with 0.  Otherwise, if an error
 occurs, it will exit with a non-zero value.
-