- Notifications
You must be signed in to change notification settings - Fork 15.3k
[AMDGPU] Make rotr illegal #166558
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
base: main
Are you sure you want to change the base?
[AMDGPU] Make rotr illegal #166558
Changes from 1 commit
b6f5f88 165f4b6 3e546d7 14ac60c 181c625 9a9658c File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| | @@ -353,16 +353,17 @@ define hidden void @shuffle5341ud2(ptr addrspace(1) %in0, ptr addrspace(1) %out0 | |||||
| ; GFX10-NEXT: s_waitcnt vmcnt(0) expcnt(0) lgkmcnt(0) | ||||||
| ; GFX10-NEXT: global_load_dword v0, v[0:1], off | ||||||
| ; GFX10-NEXT: s_waitcnt vmcnt(0) | ||||||
| ; GFX10-NEXT: v_alignbit_b32 v0, v0, v0, 16 | ||||||
| ; GFX10-NEXT: v_perm_b32 v0, v0, v0, 0x5040706 | ||||||
| ||||||
| ; FIXME: produce v_alignbit_b32 v2, v2, s0, 24 instead of v_perm |
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.
Do you have a plan for these? It feels like you're going to end up adding fshr peepholes to replace the rotr ones?
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.
Do you have a plan for these?
My plan is to hope @jrbyrnes picks it up :) At the moment I don't understand why his #70240 removed this check of yours:
| // Check that we haven't just recreated the same FSHR node. |
It feels like you're going to end up adding fshr peepholes to replace the rotr ones?
I don't think there are any peepholes. It is just that PerformDAGCombine's FSHR case calls matchPERM but the ROTR case does not.
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.
I reinstated the check for recreating the same FSHR node.
Uh oh!
There was an error while loading. Please reload this page.