llvmbot wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-clang Author: Kazu Hirata (kazutakahirata) <details> <summary>Changes</summary> --- Full diff: https://github.com/llvm/llvm-project/pull/140663.diff 5 Files Affected: - (modified) clang/docs/BoundsSafety.rst (+1-1) - (modified) clang/docs/BoundsSafetyAdoptionGuide.rst (+1-1) - (modified) clang/docs/HIPSupport.rst (+1-1) - (modified) clang/docs/ReleaseNotes.rst (+4-4) - (modified) clang/docs/UsersManual.rst (+2-2) ``````````diff diff --git a/clang/docs/BoundsSafety.rst b/clang/docs/BoundsSafety.rst index 4b70b34eb4100..519c7b685e60d 100644 --- a/clang/docs/BoundsSafety.rst +++ b/clang/docs/BoundsSafety.rst @@ -664,7 +664,7 @@ In C, arrays on function prototypes are promoted (or "decayed") to a pointer to its first element (e.g., ``&arr[0]``). In ``-fbounds-safety``, arrays are also decayed to pointers, but with the addition of an implicit bounds annotation, which includes variable-length arrays (VLAs). As shown in the following example, -arrays on function prototypes are decalyed to corresponding ``__counted_by`` +arrays on function prototypes are decayed to corresponding ``__counted_by`` pointers. .. code-block:: c diff --git a/clang/docs/BoundsSafetyAdoptionGuide.rst b/clang/docs/BoundsSafetyAdoptionGuide.rst index 9998ce58e67c1..947a236080586 100644 --- a/clang/docs/BoundsSafetyAdoptionGuide.rst +++ b/clang/docs/BoundsSafetyAdoptionGuide.rst @@ -39,7 +39,7 @@ Annotate pointers on struct fields and function parameters if they are pointing to an array of object, with appropriate bounds annotations. Please see :doc:`BoundsSafety` to learn what kind of bounds annotations are available and their semantics. Note that local pointer variables typically don't need bounds -annotations because they are implicitely a wide pointer (``__bidi_indexable``) +annotations because they are implicitly a wide pointer (``__bidi_indexable``) that automatically carries the bounds information. Address compiler diagnostics diff --git a/clang/docs/HIPSupport.rst b/clang/docs/HIPSupport.rst index dfc27089f9d4d..051a253969943 100644 --- a/clang/docs/HIPSupport.rst +++ b/clang/docs/HIPSupport.rst @@ -259,7 +259,7 @@ In other scenarios, calling virtual functions is not allowed. Explanation ----------- -An object constructed on the device side contains a pointer to the virtual function table on the device side, which is not accessible in host code, and vice versa. Thus, trying to invoke virtual functions from a context different from where the object was constructed will be disallowed because the appropriate virtual table cannot be accessed. The virtual function tables for offloading devices with different architecures are different, therefore trying to invoke virtual functions from an offloading device with a different architecture than where the object is constructed is also disallowed. +An object constructed on the device side contains a pointer to the virtual function table on the device side, which is not accessible in host code, and vice versa. Thus, trying to invoke virtual functions from a context different from where the object was constructed will be disallowed because the appropriate virtual table cannot be accessed. The virtual function tables for offloading devices with different architectures are different, therefore trying to invoke virtual functions from an offloading device with a different architecture than where the object is constructed is also disallowed. Example Usage ------------- diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst index d756f7a3a3f70..0173aca20590f 100644 --- a/clang/docs/ReleaseNotes.rst +++ b/clang/docs/ReleaseNotes.rst @@ -647,7 +647,7 @@ Bug Fixes to Compiler Builtins - ``__is_trivially_relocatable`` has been deprecated, and uses should be replaced by ``__builtin_is_cpp_trivially_relocatable``. Note that, it is generally unsafe to ``memcpy`` non-trivially copyable types that - are ``__builtin_is_cpp_trivially_relocatable``. It is recommanded to use + are ``__builtin_is_cpp_trivially_relocatable``. It is recommended to use ``__builtin_trivially_relocate`` instead. Bug Fixes to Attribute Support @@ -703,7 +703,7 @@ Bug Fixes to C++ Support - Fix crash when evaluating the trailing requires clause of generic lambdas which are part of a pack expansion. - Fixes matching of nested template template parameters. (#GH130362) -- Correctly diagnoses template template paramters which have a pack parameter +- Correctly diagnoses template template parameters which have a pack parameter not in the last position. - Disallow overloading on struct vs class on dependent types, which is IFNDR, as this makes the problem diagnosable. @@ -712,7 +712,7 @@ Bug Fixes to C++ Support - Clang now correctly parses ``if constexpr`` expressions in immediate function context. (#GH123524) - Fixed an assertion failure affecting code that uses C++23 "deducing this". (#GH130272) - Clang now properly instantiates destructors for initialized members within non-delegating constructors. (#GH93251) -- Correctly diagnoses if unresolved using declarations shadows template paramters (#GH129411) +- Correctly diagnoses if unresolved using declarations shadows template parameters (#GH129411) - Fixed C++20 aggregate initialization rules being incorrectly applied in certain contexts. (#GH131320) - Clang was previously coalescing volatile writes to members of volatile base class subobjects. The issue has been addressed by propagating qualifiers during derived-to-base conversions in the AST. (#GH127824) @@ -819,7 +819,7 @@ Windows Support which makes ``offsetof`` provided by Microsoft's ``<stddef.h>`` to be defined correctly. (#GH59689) -- Clang now can process the `i128` and `ui128` integeral suffixes when MSVC +- Clang now can process the `i128` and `ui128` integral suffixes when MSVC extensions are enabled. This allows for properly processing ``intsafe.h`` in the Windows SDK. diff --git a/clang/docs/UsersManual.rst b/clang/docs/UsersManual.rst index d3a0a3a46db33..eb9a812f0c1c9 100644 --- a/clang/docs/UsersManual.rst +++ b/clang/docs/UsersManual.rst @@ -3650,7 +3650,7 @@ below. If multiple flags are present, the last one is used. By default, Clang does not emit type information for types that are defined but not used in a program. To retain the debug info for these unused types, the negation **-fno-eliminate-unused-debug-types** can be used. - This can be particulary useful on Windows, when using NATVIS files that + This can be particularly useful on Windows, when using NATVIS files that can reference const symbols that would otherwise be stripped, even in full debug or standalone debug modes. @@ -4267,7 +4267,7 @@ nosvm ^^^^^ Clang supports this attribute to comply to OpenCL v2.0 conformance, but it -does not have any effect on the IR. For more details reffer to the specification +does not have any effect on the IR. For more details refer to the specification `section 6.7.2 <https://www.khronos.org/registry/cl/specs/opencl-2.0-openclc.pdf#49>`_ `````````` </details> https://github.com/llvm/llvm-project/pull/140663 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
