Author: Stephan T. Lavavej Date: 2021-12-14T14:19:42-08:00 New Revision: 8bd106a891726f6542c9364ff4041764a62aa2b7
URL: https://github.com/llvm/llvm-project/commit/8bd106a891726f6542c9364ff4041764a62aa2b7 DIFF: https://github.com/llvm/llvm-project/commit/8bd106a891726f6542c9364ff4041764a62aa2b7.diff LOG: [NFC] Fix typos in release notes. Reviewed By: ldionne, Mordante, MaskRay Differential Revision: https://reviews.llvm.org/D115685 Added: Modified: clang-tools-extra/docs/ReleaseNotes.rst clang/docs/ReleaseNotes.rst libcxx/docs/ReleaseNotes.rst lld/docs/ReleaseNotes.rst polly/docs/ReleaseNotes.rst Removed: ################################################################################ diff --git a/clang-tools-extra/docs/ReleaseNotes.rst b/clang-tools-extra/docs/ReleaseNotes.rst index e95e2a297751a..341eb82a1e903 100644 --- a/clang-tools-extra/docs/ReleaseNotes.rst +++ b/clang-tools-extra/docs/ReleaseNotes.rst @@ -172,5 +172,5 @@ Improvements to pp-trace The improvements are... -Clang-tidy visual studio plugin +Clang-tidy Visual Studio plugin ------------------------------- diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst index 07953a8fb0fdc..2993b20f76343 100644 --- a/clang/docs/ReleaseNotes.rst +++ b/clang/docs/ReleaseNotes.rst @@ -237,7 +237,7 @@ Floating Point Support in Clang rather than -ffp-contract=fast, and the documentation of these features has been clarified. Previously, the documentation claimed that -ffp-model=precise was the default, but this was incorrect because the precise model implied - -ffp-contract=fast, wheras the (now corrected) default behavior is + -ffp-contract=fast, whereas the (now corrected) default behavior is -ffp-contract=on. -ffp-model=precise is now exactly the default mode of the compiler. @@ -276,7 +276,7 @@ clang-format - Option ``AllowShortEnumsOnASingleLine: false`` has been improved, it now correctly places the opening brace according to ``BraceWrapping.AfterEnum``. -- Option ``QualifierAligment`` has been added in order to auto-arrange the +- Option ``QualifierAlignment`` has been added in order to auto-arrange the positioning of specifiers/qualifiers `const` `volatile` `static` `inline` `constexpr` `restrict` in variable and parameter declarations to be either ``Right`` aligned diff --git a/libcxx/docs/ReleaseNotes.rst b/libcxx/docs/ReleaseNotes.rst index 16ec6671f094d..5f45c3c5e7743 100644 --- a/libcxx/docs/ReleaseNotes.rst +++ b/libcxx/docs/ReleaseNotes.rst @@ -56,7 +56,7 @@ New Features randomization of both sides of partition for ``std::nth_element``) - Floating-point support for ``std::to_chars`` support has been added. - Thanks to Stephan T. Lavavej and Microsoft for providing their implemention + Thanks to Stephan T. Lavavej and Microsoft for providing their implementation to libc++. API Changes @@ -65,11 +65,11 @@ API Changes - The functions ``std::atomic<T*>::fetch_(add|sub)`` and ``std::atomic_fetch_(add|sub)`` no longer accept a function pointer. While this is technically an API break, the invalid syntax isn't supported by - libstc++ and MSVC STL. See https://godbolt.org/z/49fvzz98d. + libstdc++ and MSVC STL. See https://godbolt.org/z/49fvzz98d. - The call of the functions ``std::atomic_(add|sub)(std::atomic<T*>*, ...)`` with the explicit template argument ``T`` are now ill-formed. While this is - technically an API break, the invalid syntax isn't supported by libstc++ and + technically an API break, the invalid syntax isn't supported by libstdc++ and MSVC STL. See https://godbolt.org/z/v9959re3v. Due to this change it's now possible to call these functions with the @@ -125,7 +125,7 @@ Build System Changes culminated in over 5 diff erent ways to build the runtimes, which made it impossible to maintain with a good level of support. Starting with this release, the runtimes support exactly two ways of being built, which should cater to all use-cases. Furthermore, - these builds are as lightweight as possible and will work consistently even when targetting + these builds are as lightweight as possible and will work consistently even when targeting embedded platforms, which used not to be the case. Please see the documentation on building libc++ to see those two ways of building and migrate over to the appropriate build instructions as soon as possible. diff --git a/lld/docs/ReleaseNotes.rst b/lld/docs/ReleaseNotes.rst index a2456fc46689b..f7e099b9cf6ea 100644 --- a/lld/docs/ReleaseNotes.rst +++ b/lld/docs/ReleaseNotes.rst @@ -31,7 +31,7 @@ ELF Improvements * ``e_entry`` no longer falls back to the address of ``.text`` if the entry symbol does not exist. Instead, a value of 0 will be written. (`D110014 <https://reviews.llvm.org/D110014>`_) -* If ``-Map`` is specified, ``--cref`` will be printted to the specified file. +* If ``-Map`` is specified, ``--cref`` will be printed to the specified file. (`D114663 <https://reviews.llvm.org/D114663>`_) Architecture specific changes: diff --git a/polly/docs/ReleaseNotes.rst b/polly/docs/ReleaseNotes.rst index bcc95f55cfa0c..9ee6eac6ec188 100644 --- a/polly/docs/ReleaseNotes.rst +++ b/polly/docs/ReleaseNotes.rst @@ -19,7 +19,7 @@ In Polly 14 the following important changes have been incorporated. -polly-isl-arg=--no-schedule-serialize-sccs - The command line option -polly-loopfusion-greedy has been added. - This will agressively try to fuse any loop regardless of + This will aggressively try to fuse any loop regardless of profitability. The is what users might have expected what -polly-opt-fusion=max would do. _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits