[llvm] [AMDGPU][NFC] Added test for live-in CSR SGPR used partially giving MachineVerifier error (PR #126696)

[Pravin Jagtap via llvm-commits]

pravinjagtap wrote:

[AMD Official Use Only - AMD Internal Distribution Only]

Following stack might help you understand the workflow:
✅ #128648 AMDGPU: Handle demanded subvectors for readfirstlane<https://app.graphite.dev//github/pr/llvm/llvm-project/128648?ref=gt-pasteable-stack> +68/-30
✅ #128647 AMDGPU: Reduce readfirstlane for single demanded vector element<https://app.graphite.dev//github/pr/llvm/llvm-project/128647?ref=gt-pasteable-stack> +78/-31
✅ #128646 AMDGPU: Simplify demanded vector elts of readfirstlane sources<https://app.graphite.dev//github/pr/llvm/llvm-project/128646?ref=gt-pasteable-stack> +7/-8
✅ #128645 AMDGPU: Add baseline tests for simplify elts of readfirstlane<https://app.graphite.dev//github/pr/llvm/llvm-project/128645?ref=gt-pasteable-stack> +444/-0


________________________________
From: Vikash Gupta ***@***.***>
Sent: Tuesday, February 25, 2025 11:55 AM
To: llvm/llvm-project ***@***.***>
Cc: Jagtap, Pravin ***@***.***>; Team mention ***@***.***>
Subject: Re: [llvm/llvm-project] [AMDGPU][NFC] Added test for live-in CSR SGPR used partially giving MachineVerifier error (PR #126696)

Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.


Can you stack the PR #126926<https://github.com/llvm/llvm-project/pull/126926> along with it? This PR is supposed to fix the error you mentioned in this test. We should be able to see how the proposed fix changes the test if they are stacked together.

In order to stack PRs (assuming graphite), don't we need to create new PRs completely for test & patch as both of these branches as for now are independent & created from my forked repo's main. I am thinking for this time to merge it in upstream & rebase it for the patch PR, that might do the trick for now. Will take care of stacking in such future cases!

—
Reply to this email directly, view it on GitHub<https://github.com/llvm/llvm-project/pull/126696#issuecomment-2680768602>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGK64FR5MYOBP4QLRFYRVPL2RQEFLAVCNFSM6AAAAABW4NTE7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBQG43DQNRQGI>.
You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>

[vg0204]vg0204 left a comment (llvm/llvm-project#126696)<https://github.com/llvm/llvm-project/pull/126696#issuecomment-2680768602>

Can you stack the PR #126926<https://github.com/llvm/llvm-project/pull/126926> along with it? This PR is supposed to fix the error you mentioned in this test. We should be able to see how the proposed fix changes the test if they are stacked together.

In order to stack PRs (assuming graphite), don't we need to create new PRs completely for test & patch as both of these branches as for now are independent & created from my forked repo's main. I am thinking for this time to merge it in upstream & rebase it for the patch PR, that might do the trick for now. Will take care of stacking in such future cases!

—
Reply to this email directly, view it on GitHub<https://github.com/llvm/llvm-project/pull/126696#issuecomment-2680768602>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGK64FR5MYOBP4QLRFYRVPL2RQEFLAVCNFSM6AAAAABW4NTE7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBQG43DQNRQGI>.
You are receiving this because you are on a team that was mentioned.Message ID: ***@***.***>


https://github.com/llvm/llvm-project/pull/126696