Update for Clang 10 release notes

[Mordante]

Summary

This contains the update for the release notes for D73007 and D73434.

You already cherry-picked the changes for D73007.
Can you cherry-pick c03349e40f21 for D73434?

[merge_guards_bot]

Unit tests: unknown.

clang-tidy: unknown.

clang-format: unknown.

Build artifacts: diff.json, console-log.txt

Pre-merge checks is in beta. Report issue. Please join beta or enable it for your project.

[hans]

Looks good to me, go a head and commit it to the branch.

Can you cherry-pick c03349e40f21 for D73434?

Cherry-picked in 72e9e378c545aadb213e95892d50aa0b1248e018

[Mordante]

Phab registered the commit, but didn't close this review.

clang/docs/ReleaseNotes.rst

- -Wtautological-bitwise-compare is a new warning group.  This group has the
   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
   when mixing bitwise-and (&) and bitwise-or (|) operator with the
   conditional operator (?:).
 - -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. It is now part of -Wall.
+  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
+  disabled in macros and template instantiations.
 
 Non-comprehensive list of changes in this release
 -------------------------------------------------
 
 * In both C and C++ (C17 ``6.5.6p8``, C++ ``[expr.add]``), pointer arithmetic is
   only permitted within arrays. In particular, the behavior of a program is not
   defined if it adds a non-zero offset (or in C, any offset) to a null pointer,
   or if it forms a null pointer by subtracting an integer from a non-null