-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[libc++] Properly implement array cookies in the ARM ABI #160182
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
Open
ldionne
wants to merge
1
commit into
llvm:main
Choose a base branch
from
ldionne:review/fix-array-cookie-on-arm
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+100
−5
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,12 +26,12 @@ _LIBCPP_BEGIN_NAMESPACE_STD | |
// Trait representing whether a type requires an array cookie at the start of its allocation when | ||
// allocated as `new T[n]` and deallocated as `delete[] array`. | ||
// | ||
// Under the Itanium C++ ABI [1], we know that an array cookie is available unless `T` is trivially | ||
// destructible and the call to `operator delete[]` is not a sized operator delete. Under ABIs other | ||
// than the Itanium ABI, we assume there are no array cookies. | ||
// Under the Itanium C++ ABI [1] and the ARM ABI which derives from it, we know that an array cookie is available | ||
// unless `T` is trivially destructible and the call to `operator delete[]` is not a sized operator delete. Under | ||
// other ABIs, we assume there are no array cookies. | ||
// | ||
// [1]: https://itanium-cxx-abi.github.io/cxx-abi/abi.html#array-cookies | ||
#ifdef _LIBCPP_ABI_ITANIUM | ||
#if defined(_LIBCPP_ABI_ITANIUM) || defined(_LIBCPP_ABI_ARM) | ||
// TODO: Use a builtin instead | ||
// TODO: We should factor in the choice of the usual deallocation function in this determination. | ||
template <class _Tp> | ||
|
@@ -41,13 +41,73 @@ template <class _Tp> | |
struct __has_array_cookie : false_type {}; | ||
#endif | ||
|
||
// Return the array cookie located before the given pointer. | ||
// | ||
// In the Itanium ABI | ||
// ------------------ | ||
// The array cookie is stored immediately before the first element of the array. If the preferred alignment | ||
// of array elements (which is different from the ABI alignment) is more than that of size_t, additional | ||
// padding bytes exist before the array cookie. Assuming array elements of size and alignment 16 bytes, that | ||
// gives us the following layout: | ||
// | ||
// |ooooooooxxxxxxxxaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbccccccccccccccccdddddddddddddddd| | ||
// ^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
// | ^^^^^^^^ | | ||
// | | array elements | ||
// padding | | ||
// array cookie | ||
// | ||
// In practice, it is sufficient to read the bytes immediately before the first array element. | ||
// | ||
// | ||
// In the ARM ABI | ||
// -------------- | ||
// The array cookie is stored at the very start of the allocation and it has the following form: | ||
// | ||
// struct array_cookie { | ||
// std::size_t element_size; // element_size != 0 | ||
// std::size_t element_count; | ||
// }; | ||
// | ||
// Assuming elements of size and alignment 32 bytes, this gives us the following layout: | ||
// | ||
// |xxxxxxxxXXXXXXXXooooooooooooooooaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb| | ||
// ^^^^^^^^ ^^^^^^^^^^^^^^^^ | ||
// | ^^^^^^^^ | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
// element size | padding | | ||
// element count array elements | ||
// | ||
// We calculate the starting address of the allocation by taking into account the ABI (not the preferred) | ||
// alignment of the type. | ||
template <class _Tp> | ||
// Avoid failures when -fsanitize-address-poison-custom-array-cookie is enabled | ||
_LIBCPP_HIDE_FROM_ABI _LIBCPP_NO_SANITIZE("address") size_t __get_array_cookie(_Tp const* __ptr) { | ||
static_assert( | ||
__has_array_cookie<_Tp>::value, "Trying to access the array cookie of a type that is not guaranteed to have one"); | ||
size_t const* __cookie = reinterpret_cast<size_t const*>(__ptr) - 1; // TODO: Use a builtin instead | ||
|
||
#if defined(_LIBCPP_ABI_ITANIUM) | ||
|
||
size_t const* __cookie = reinterpret_cast<size_t const*>(__ptr) - 1; | ||
return *__cookie; | ||
|
||
#elif defined(_LIBCPP_ABI_ARM) | ||
|
||
struct _ArrayCookie { | ||
size_t __element_size; | ||
size_t __element_count; | ||
}; | ||
|
||
size_t __cookie_size_with_padding = // max(sizeof(_ArrayCookie), alignof(T)) | ||
sizeof(_ArrayCookie) < alignof(_Tp) ? alignof(_Tp) : sizeof(_ArrayCookie); | ||
char const* __allocation_start = reinterpret_cast<char const*>(__ptr) - __cookie_size_with_padding; | ||
_ArrayCookie const* __cookie = reinterpret_cast<_ArrayCookie const*>(__allocation_start); | ||
return __cookie->__element_count; | ||
Comment on lines
+95
to
+104
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Couldn't we simplify this to struct [[__gnu__::__aligned__(alignof(_Tp)), __gnu__::__may_alias__]] _ArrayCookie {
size_t __element_size;
size_t __element_count;
};
auto __cookie = reinterpret_cast<const _ArrayCookie*>(__ptr) - 1;
return __cookie->__element_count; |
||
|
||
#else | ||
|
||
static_assert(sizeof(_Tp) == 0, "This function is not implemented for this ABI"); | ||
|
||
#endif | ||
} | ||
|
||
_LIBCPP_END_NAMESPACE_STD | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reference manual for the ARM ABI somewhere? Could we link to that from here?