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 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
