-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[Support] Recycler: Enforce minimum allocation size #121425
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
Merged
optimisan
merged 2 commits into
main
from
users/Akshat-Oke/01-01-_support_recycler_enforce_minimum_allocation_size
Jan 6, 2025
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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 |
---|---|---|
@@ -0,0 +1,46 @@ | ||
//===--- unittest/Support/RecyclerTest.cpp --------------------------------===// | ||
// | ||
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. | ||
// See https://llvm.org/LICENSE.txt for license information. | ||
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception | ||
// | ||
//===----------------------------------------------------------------------===// | ||
|
||
#include "llvm/Support/Recycler.h" | ||
#include "llvm/Support/AllocatorBase.h" | ||
#include "gtest/gtest.h" | ||
|
||
using namespace llvm; | ||
|
||
namespace { | ||
|
||
struct Object1 { | ||
char Data[1]; | ||
}; | ||
|
||
class DecoratedMallocAllocator : public MallocAllocator { | ||
public: | ||
int DeallocCount = 0; | ||
|
||
template <typename T> void Deallocate(T *Ptr) { | ||
DeallocCount++; | ||
MallocAllocator::Deallocate(Ptr); | ||
} | ||
}; | ||
|
||
TEST(RecyclerTest, RecycleAllocation) { | ||
DecoratedMallocAllocator Allocator; | ||
// Recycler needs size to be atleast 8 bytes. | ||
Recycler<Object1, 8, 8> R; | ||
Object1 *A1 = R.Allocate(Allocator); | ||
Object1 *A2 = R.Allocate(Allocator); | ||
R.Deallocate(Allocator, A2); | ||
Object1 *A3 = R.Allocate(Allocator); | ||
EXPECT_EQ(A2, A3); // reuse the deallocated object. | ||
R.Deallocate(Allocator, A1); | ||
R.Deallocate(Allocator, A3); | ||
R.clear(Allocator); // Should deallocate A1 and A3. | ||
EXPECT_EQ(Allocator.DeallocCount, 2); | ||
} | ||
|
||
} // end anonymous namespace |
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 way to test the static_assert fails in the < 8 case?
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.
Don't think we have any infrastructure in LLVM for "this should fail to compile". If it were SFINAE'd then we could static_assert that something fails to compile, but static_asserts aren't themselves SFINAE, so it'd mean adding more metaprogramming infrastructure that's presumably not otherwise needed (& wouldn't test the static_assert itself, but the SFINAE trap)