Author: Peter Wu
Date: 2020-03-04T01:31:10Z
New Revision: 3ef42c184ac355ed482e3cae41c92cb205a116ae
URL:
https://github.com/llvm/llvm-project/commit/3ef42c184ac355ed482e3cae41c92cb205a116ae
DIFF:
https://github.com/llvm/llvm-project/commit/3ef42c184ac355ed482e3cae41c92cb205a116ae.diff
LOG: ReleaseNotes: Formatting and typo fixes.
Added:
Modified:
clang/docs/ReleaseNotes.rst
llvm/docs/ReleaseNotes.rst
Removed:
diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst
index a6ff29c630ed..52a249f8fcdb 100644
--- a/clang/docs/ReleaseNotes.rst
+++ b/clang/docs/ReleaseNotes.rst
@@ -47,36 +47,36 @@ Major New Features
Improvements to Clang's diagnostics
^^^
-- -Wtautological-overlap-compare will warn on negative numbers and non-int
+- ``-Wtautological-overlap-compare`` will warn on negative numbers and non-int
types.
-- -Wtautological-compare for self comparisons and
- -Wtautological-overlap-compare will now look through member and array
+- ``-Wtautological-compare`` for self comparisons and
+ ``-Wtautological-overlap-compare`` will now look through member and array
access to determine if two operand expressions are the same.
-- -Wtautological-bitwise-compare is a new warning group. This group has the
+- ``-Wtautological-bitwise-compare`` is a new warning group. This group has
the
current warning which diagnoses the tautological comparison of a bitwise
operation and a constant. The group also has the new warning which diagnoses
when a bitwise-or with a non-negative value is converted to a bool, since
that bool will always be true.
-- -Wbitwise-conditional-parentheses will warn on operator precedence issues
+- ``-Wbitwise-conditional-parentheses`` will warn on operator precedence issues
when mixing bitwise-and (&) and bitwise-or (|) operator with the
conditional operator (?:).
-- -Wrange-loop-analysis got several improvements. It no longer warns about a
+- ``-Wrange-loop-analysis`` got several improvements. It no longer warns about
a
copy being made when the result is bound to an rvalue reference. It no longer
warns when an object of a small, trivially copyable type is copied. The
- warning now offers fixits. Excluding -Wrange-loop-bind-reference it is now
- part of -Wall. To reduce the number of false positives the diagnostic is
+ warning now offers fix-its. Excluding ``-Wrange-loop-bind-reference`` it is
now
+ part of ``-Wall``. To reduce the number of false positives the diagnostic is
disabled in macros and template instantiations.
-- -Wmisleading-indentation has been added. This warning is similar to the GCC
+- ``-Wmisleading-indentation`` has been added. This warning is similar to the
GCC
warning of the same name. It warns about statements that are indented as if
they were part of a if/else/for/while statement but are not semantically
part of that if/else/for/while.
-- -Wbitwise-op-parentheses and -Wlogical-op-parentheses are disabled by
default.
+- ``-Wbitwise-op-parentheses`` and ``-Wlogical-op-parentheses`` are disabled
by default.
Non-comprehensive list of changes in this release
-
@@ -95,15 +95,15 @@ Non-comprehensive list of changes in this release
learned to sanitize pre/post increment/decrement of types with bit width
smaller than ``int``.
-* For X86 target, -march=skylake-avx512, -march=icelake-client,
- -march=icelake-server, -march=cascadelake, -march=cooperlake will default to
+* For X86 target, ``-march=skylake-avx512``, ``-march=icelake-client``,
+ ``-march=icelake-server``, ``-march=cascadelake``, ``-march=cooperlake``
will default to
not using 512-bit zmm registers in vectorized code unless 512-bit intrinsics
are used in the source code. 512-bit operations are known to cause the CPUs
to run at a lower frequency which can impact performance. This behavior can
be
- changed by passing -mprefer-vector-width=512 on the command line.
+ changed by passing ``-mprefer-vector-width=512`` on the command line.
-* clang now defaults to ``.init_array`` on Linux. It used to use ``.ctors`` if
- the found gcc installation is older than 4.7.0. Add ``-fno-use-init-array``
to
+* Clang now defaults to ``.init_array`` on Linux. It used to use ``.ctors`` if
+ the found GCC installation is older than 4.7.0. Add ``-fno-use-init-array``
to
get the old behavior (``.ctors``).
* The behavior of the flag ``-flax-vector-conversions`` has been modified to
@@ -126,16 +126,16 @@ Non-comprehensive list of changes in this release
New Compiler Flags
--
-- The -fgnuc-version= flag now controls the value of ``__GNUC__`` and related
+- The ``-fgnuc-version=`` flag now controls the value of ``__GNUC__`` and
related
macros. This flag does not enable or disable any GCC extensions implemented
in
Clan
