-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[SPARC] Fix-forward #154950 by returning true if SP::V8BAR is handled #162424
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
Conversation
…dled Buildbot report: https://lab.llvm.org/buildbot/#/builders/24/builds/13433 Use-after-poison happens because after SP::V8BAR is handled, it erases MI, which should thereafter not be inspected by ExpandPostRA::run.
@llvm/pr-subscribers-backend-sparc Author: Thurston Dang (thurstond) ChangesBuildbot report: https://lab.llvm.org/buildbot/#/builders/24/builds/13433 Use-after-poison happens because after SP::V8BAR is handled, it erases MI, which should thereafter not be inspected by ExpandPostRA::run. Full diff: https://github.com/llvm/llvm-project/pull/162424.diff 1 Files Affected:
diff --git a/llvm/lib/Target/Sparc/SparcInstrInfo.cpp b/llvm/lib/Target/Sparc/SparcInstrInfo.cpp
index c0cd0176efa30..f66eb9dbee2dc 100644
--- a/llvm/lib/Target/Sparc/SparcInstrInfo.cpp
+++ b/llvm/lib/Target/Sparc/SparcInstrInfo.cpp
@@ -668,6 +668,7 @@ bool SparcInstrInfo::expandPostRAPseudo(MachineInstr &MI) const {
.addImm(-1);
MIBundleBuilder(MBB, InstSTBAR, InstLDSTUB);
MBB.erase(MI);
+ return true;
}
}
return false;
|
Compilation is running slowly, I will check if the test(s) needs updating |
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/18/builds/21805 Here is the relevant piece of the build log for the reference
|
…#162424) Use-after-poison happens because after SP::V8BAR is handled, it erases MI, which therefore should not be inspected by `ExpandPostRA::run()`. This fixes a buildbot-reported issue from #154950 (https://lab.llvm.org/buildbot/#/builders/24/builds/13433).
Use-after-poison happens because after SP::V8BAR is handled, it erases MI, which should therefore not be inspected by
ExpandPostRA::run()
.This fixes a buildbot reported issue from #154950 (https://lab.llvm.org/buildbot/#/builders/24/builds/13433).