Skip to content

Add release note for #95264 #96116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

ldionne
Copy link
Member

@ldionne ldionne commented Jun 19, 2024

No description provided.

@ldionne ldionne requested a review from tstellar June 19, 2024 20:51
@ldionne ldionne requested a review from a team as a code owner June 19, 2024 20:51
@ldionne ldionne added this to the LLVM 18.X Release milestone Jun 19, 2024
@llvmbot llvmbot added the libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. label Jun 19, 2024
@llvmbot
Copy link
Member

llvmbot commented Jun 19, 2024

@llvm/pr-subscribers-libcxx

Author: Louis Dionne (ldionne)

Changes

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

1 Files Affected:

  • (modified) libcxx/docs/ReleaseNotes/18.rst (+9)
diff --git a/libcxx/docs/ReleaseNotes/18.rst b/libcxx/docs/ReleaseNotes/18.rst
index 7ea13e6943dd4..3e19e7c33f6af 100644
--- a/libcxx/docs/ReleaseNotes/18.rst
+++ b/libcxx/docs/ReleaseNotes/18.rst
@@ -328,6 +328,15 @@ ABI Affecting Changes
   done to fix `#70494 <https://github.com/llvm/llvm-project/issues/70494>`_ and the vendor communication is handled
   in `#70820 <https://github.com/llvm/llvm-project/issues/70820>`_.
 
+- LLVM 18.1.8 Fixed an issue that caused ``std::string`` to pass an incorrect size to ``allocator_traits::deallocate``
+  when deallocating memory. The impact is different depending on a few factors:
+  - Users who don't use a custom allocator in ``std::string`` and don't enable sized deallocation (which is
+    off by default in Clang 18) will not be affected. This is expected to be the vast majority of users.
+  - Users who don't use a custom allocator in ``std::string`` but are enabling sized deallocation (e.g. with
+    ``-fsized-deallocation``) will notice that ``operator delete(void*, size_t)`` is now being passed the correct
+    size. This likely has no impact if they were not customizing ``operator delete``.
+  - Users who use a custom allocator in ``std::string`` will notice that they now get passed the correct allocation
+    size upon deallocation.
 
 Build System Changes
 --------------------

@ldionne
Copy link
Member Author

ldionne commented Jun 24, 2024

Gentle ping @tstellar, do we want to merge this?

The CI issues are unrelated.

@tstellar
Copy link
Collaborator

We don't have a great way to add release notes after the final release. I added this to the release announcement do you think that is enough?

@ldionne
Copy link
Member Author

ldionne commented Jun 24, 2024

We don't have a great way to add release notes after the final release. I added this to the release announcement do you think that is enough?

Yes I think that is fine.

@ldionne ldionne closed this Jun 24, 2024
@ldionne ldionne deleted the review/llvm-18-release-note-for-string branch June 24, 2024 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi.
Projects
Status: Needs Triage
Development

Successfully merging this pull request may close these issues.

3 participants