Skip to content

Conversation

llvmbot
Copy link
Member

@llvmbot llvmbot commented Jan 9, 2023

These new debug values get inserted after the place where the spill
happens, which means they won't be reached by the reverse traversal of
basic block instructions. This would crash or fail assertions if they
contained any virtual registers to be replaced. We can manually handle
the new debug values right away to resolve this.

Fixes llvm/llvm-project#59172

Reviewed By: StephenTozer

Differential Revision: https://reviews.llvm.org/D139590

(cherry picked from commit 87f57f4)
@llvmbot
Copy link
Member Author

llvmbot commented Jan 9, 2023

@SLTozer What do you think about merging this PR to the release branch?

@cuviper
Copy link
Member

cuviper commented Jan 9, 2023

Looks like the test needs utils/update_llc_test_checks.py for some incidental differences.

@nikic
Copy link
Contributor

nikic commented Jan 10, 2023

New PR at #228 should fix the test failure. Can't close this one myself though.

@tru tru closed this Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RegAllocFast::runOnMachineFunction misses a virtual register
4 participants