-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[AMDGPU][TTI] Add Target Hook for Instruction Uniformity (getInstructionUniformity) #137639
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
PankajDwivedi-25
wants to merge
2
commits into
llvm:main
Choose a base branch
from
PankajDwivedi-25:users/pkd-25/make-ui-operand-aware
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.
Open
Changes from 1 commit
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
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
25 changes: 25 additions & 0 deletions
25
llvm/test/Analysis/UniformityAnalysis/AMDGPU/uniform_intrinsic.ll
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,25 @@ | ||
; RUN: opt -mtriple amdgcn-unknown-amdhsa -passes='print<uniformity>' -disable-output %s 2>&1 | FileCheck %s | ||
|
||
; CHECK: ALL VALUES UNIFORM | ||
define amdgpu_kernel void @permlane64_constant(ptr addrspace(1) %out) { | ||
%v = call i32 @llvm.amdgcn.permlane64(i32 7) | ||
store i32 %v, ptr addrspace(1) %out | ||
ret void | ||
} | ||
|
||
; CHECK: ALL VALUES UNIFORM | ||
define amdgpu_kernel void @permlane64_uniform(ptr addrspace(1) %out, i32 %src) { | ||
%v = call i32 @llvm.amdgcn.permlane64(i32 %src) | ||
store i32 %v, ptr addrspace(1) %out | ||
ret void | ||
} | ||
|
||
; CHECK: DIVERGENT: %tid = call i32 @llvm.amdgcn.workitem.id.x() | ||
; CHECK: DIVERGENT: %v = call i32 @llvm.amdgcn.permlane64.i32(i32 %tid) | ||
define amdgpu_kernel void @permlane64_nonuniform(i32 addrspace(1)* %out) { | ||
%tid = call i32 @llvm.amdgcn.workitem.id.x() | ||
%v = call i32 @llvm.amdgcn.permlane64(i32 %tid) | ||
%out_ptr = getelementptr i32, i32 addrspace(1)* %out, i32 %tid | ||
store i32 %v, i32 addrspace(1)* %out_ptr | ||
ret void | ||
} |
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.
No. Here we need to be able to query "is this operand uniform according to the current state of the uniformity analysis", either by calling back into the analysis class, or having it pass in a vector saying which operands are already known to be uniform, or something like that. Just checking for sources of divergence is not enough.
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.
Right, it was the first thing that arose in my mind while writing this. At this point, we don't have a way to call back to UI about isUniform(operand_i) or isDivergentUse(opeand_i).
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.
Maybe we don't need to actually query uniformity. We could extend the enum to have something like
InstructionUniformity::SameAsOperand0
. Not exactly that, but it's information that the calling UA can then use to decide whether a returned value is uniform based on the operands.