[llvm-branch-commits] [clang] Remove reference to reverted PR #130742 (PR #152242)

via llvm-branch-commits llvm-branch-commits at lists.llvm.org
Wed Aug 6 08:09:02 PDT 2025


llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-clang

Author: Hubert Tong (hubert-reinterpretcast)

<details>
<summary>Changes</summary>

Based on the file history in https://github.com/dtcxzyw/llvm-project/commits/main/llvm/test/CodeGen/AMDGPU/memcpy-crash-issue63986.ll, it appears #<!-- -->130742 was reverted by #<!-- -->138168 and never re-applied.

---
Full diff: https://github.com/llvm/llvm-project/pull/152242.diff


1 Files Affected:

- (modified) clang/docs/ReleaseNotes.rst (+1-1) 


``````````diff
diff --git a/clang/docs/ReleaseNotes.rst b/clang/docs/ReleaseNotes.rst
index 1c6e7fc1c0760..f4f7dd8342d92 100644
--- a/clang/docs/ReleaseNotes.rst
+++ b/clang/docs/ReleaseNotes.rst
@@ -55,7 +55,7 @@ C/C++ Language Potentially Breaking Changes
   case for old-style offsetof idioms like ``((int)(&(((struct S *)0)->field)))``, to
   ensure they are not caught by these optimizations.  It is also possible to use
   ``-fwrapv-pointer`` or   ``-fno-delete-null-pointer-checks`` to make pointer arithmetic
-  on null pointers well-defined. (#GH130734, #GH130742, #GH130952)
+  on null pointers well-defined. (#GH130734, #GH130952)
 
 C++ Specific Potentially Breaking Changes
 -----------------------------------------

``````````

</details>


https://github.com/llvm/llvm-project/pull/152242


More information about the llvm-branch-commits mailing list