-
Notifications
You must be signed in to change notification settings - Fork 15.3k
[MemProf][PGO] Prevent dropping of profile metadata during optimization #121359
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
teresajohnson
merged 3 commits into
llvm:main
from
teresajohnson:memprof_metadata_drop_fix
Jan 2, 2025
Merged
Changes from 1 commit
Commits
Show all changes
3 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
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,51 @@ | ||
| ; NOTE: Assertions have been autogenerated by utils/update_test_checks.py UTC_ARGS: --version 5 | ||
|
|
||
| ;; Test to ensure that memprof related metadata is not dropped when | ||
| ;; instructions are combined. Currently the metadata from the first instruction | ||
| ;; is kept, which prevents full loss of profile context information. | ||
|
|
||
| ; RUN: opt < %s -passes=simplifycfg -S | FileCheck %s | ||
|
|
||
| target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-i128:128-f80:128-n8:16:32:64-S128" | ||
| target triple = "x86_64-unknown-linux-gnu" | ||
|
|
||
| define dso_local noundef nonnull ptr @_Z4testb(i1 noundef zeroext %b) local_unnamed_addr #0 { | ||
| ; CHECK-LABEL: define dso_local noundef nonnull ptr @_Z4testb( | ||
| ; CHECK-SAME: i1 noundef zeroext [[B:%.*]]) local_unnamed_addr { | ||
| ; CHECK-NEXT: [[ENTRY:.*:]] | ||
| ; CHECK-NEXT: [[CALL:%.*]] = call noalias noundef nonnull dereferenceable(4) ptr @_Znwm(i64 noundef 4), !memprof [[META0:![0-9]+]], !callsite [[META3:![0-9]+]] | ||
| ; CHECK-NEXT: ret ptr [[CALL]] | ||
| ; | ||
| entry: | ||
| br i1 %b, label %if.then, label %if.else | ||
|
|
||
| if.then: ; preds = %entry | ||
| %call = call noalias noundef nonnull dereferenceable(4) ptr @_Znwm(i64 noundef 4), !memprof !0, !callsite !3 | ||
| br label %if.end | ||
|
|
||
| if.else: ; preds = %entry | ||
| %call1 = call noalias noundef nonnull dereferenceable(4) ptr @_Znwm(i64 noundef 4), !memprof !4, !callsite !7 | ||
| br label %if.end | ||
|
|
||
| if.end: ; preds = %if.else, %if.then | ||
| %x.0 = phi ptr [ %call, %if.then ], [ %call1, %if.else ] | ||
| ret ptr %x.0 | ||
| } | ||
|
|
||
|
|
||
| declare ptr @_Znwm(i64) nounwind readonly | ||
|
|
||
| !0 = !{!1} | ||
| !1 = !{!2, !"notcold"} | ||
| !2 = !{i64 -852997907418798798, i64 -2101080423462424381, i64 5188446645037944434} | ||
| !3 = !{i64 -852997907418798798} | ||
| !4 = !{!5} | ||
| !5 = !{!6, !"cold"} | ||
| !6 = !{i64 123, i64 -2101080423462424381, i64 5188446645037944434} | ||
| !7 = !{i64 123} | ||
| ;. | ||
| ; CHECK: [[META0]] = !{[[META1:![0-9]+]]} | ||
| ; CHECK: [[META1]] = !{[[META2:![0-9]+]], !"notcold"} | ||
| ; CHECK: [[META2]] = !{i64 -852997907418798798, i64 -2101080423462424381, i64 5188446645037944434} | ||
| ; CHECK: [[META3]] = !{i64 -852997907418798798} | ||
| ;. |
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.
Shouldn't this be merging the contents of the memprof and callsite metadata, rather than taking it from one of the instructions?
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.
There isn't a great way to merge them at the moment, unfortunately. They encode information about the call context and it can't currently support multiple distinct call locations. For now we pick one. In the actual case I was looking at in real code this handling was invoked by the byval argument optimization in MemCpyOptimizer though, where we aren't even combining two calls, so this change just ensures it isn't dropped unnecessarily (as you note this probably isn't the best facility to use in that code anyway).
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.
If it's not possible to correctly merge the metadata, we shouldn't include it in combineMetadata, as it will produce an incorrect result for the sink/hoist cases. It sounds like it would be sufficient for your case to only fix what MemCpyOptimizer does (to avoid merging for memprof/callsite in the first place). I'd rather not introduce incorrect merging logic in combineMetadata to cancel out incorrect code in MemCpyOptimizer...
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.
It isn't incorrect to keep one. Since it is profile metadata, it doesn't affect correctness. We can improve how this is combined in the future, but simply keeping one set for now is a reasonable heuristic.
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.
To that end, it might be better to add methods to merge the memprof related metadata, as is done for some of the other metadata types (e.g. getMergedProfMetadata), so we can keep that handling centralized with other memprof code and add TODOs for more sophisticated merging. I will do that.