Author: Hubert Tong Date: 2025-08-08T12:12:53+02:00 New Revision: 6203ddea9f3303fd988724179ec978dc0c54d966
URL: https://github.com/llvm/llvm-project/commit/6203ddea9f3303fd988724179ec978dc0c54d966 DIFF: https://github.com/llvm/llvm-project/commit/6203ddea9f3303fd988724179ec978dc0c54d966.diff LOG: Remove reference to reverted PR #130742 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. Added: Modified: clang/docs/ReleaseNotes.rst Removed: ################################################################################ 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 ----------------------------------------- _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits