-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[Attributor] New attribute to identify what byte ranges are alive for an allocation #66148
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
Conversation
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
jdoerfert
reviewed
Sep 18, 2023
shiltian
reviewed
Sep 19, 2023
72abe39
to
d40522c
Compare
d40522c
to
fa12522
Compare
jdoerfert
reviewed
Sep 27, 2023
fc82fad
to
d30f3e0
Compare
d30f3e0
to
dcc9111
Compare
jhuber6
reviewed
Oct 5, 2023
dcc9111
to
aa91883
Compare
b3f6e6c
to
df970b9
Compare
09341e7
to
b771b54
Compare
shiltian
approved these changes
Oct 19, 2023
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.
The patch is in a descent shape now.
992e925
to
7c80fa4
Compare
jdoerfert
reviewed
Oct 25, 2023
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.
The last comments are minor, should be good to be merged after
7c80fa4
to
0dd6811
Compare
f58753a
to
5e92f24
Compare
… an allocation Changes the size of allocations automatically. Only implements the case when a single range from start of the allocation is alive. Differential Revision: https://reviews.llvm.org/D157068
5e92f24
to
b36ce02
Compare
jdoerfert
approved these changes
Nov 11, 2023
zahiraam
pushed a commit
to zahiraam/llvm-project
that referenced
this pull request
Nov 20, 2023
… an allocation (llvm#66148) Changes the size of allocations automatically. For now, implements the case when a single range from start of the allocation is alive and the allocation can be reduced.
Guzhu-AMD
pushed a commit
to GPUOpen-Drivers/llvm-project
that referenced
this pull request
Nov 23, 2023
Local branch amd-gfx 7ff9492 Merged main:64f62de96609 into amd-gfx:b47928a70477 Remote branch main 754b93e [Attributor] New attribute to identify what byte ranges are alive for an allocation (llvm#66148)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes the size of allocations automatically.
For now, implements the case when a single range from start of the allocation is alive and the allocation can be reduced.