-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[NFC][indvars] Remove unused code in WidenIV::widenLoopCompare #73506
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
✅ With the latest revision this PR passed the C/C++ code formatter. |
@llvm/pr-subscribers-llvm-transforms Author: Wenju He (wenju-he) ChangesFull diff: https://github.com/llvm/llvm-project/pull/73506.diff 1 Files Affected:
diff --git a/llvm/lib/Transforms/Utils/SimplifyIndVar.cpp b/llvm/lib/Transforms/Utils/SimplifyIndVar.cpp
index a23ac41acaa58aa..a1d09fd73c29129 100644
--- a/llvm/lib/Transforms/Utils/SimplifyIndVar.cpp
+++ b/llvm/lib/Transforms/Utils/SimplifyIndVar.cpp
@@ -1493,10 +1493,6 @@ bool WidenIV::widenLoopCompare(WidenIV::NarrowIVDefUse DU) {
assert(CastWidth <= IVWidth && "Unexpected width while widening compare.");
// Widen the compare instruction.
- auto *InsertPt = getInsertPointForUses(DU.NarrowUse, DU.NarrowDef, DT, LI);
- if (!InsertPt)
- return false;
- IRBuilder<> Builder(InsertPt);
DU.NarrowUse->replaceUsesOfWith(DU.NarrowDef, DU.WideDef);
// Widen the other operand of the compare, if necessary.
|
CI clang-format error isn't related to this pr:
|
That clang-format diff seems to be coming from 7c93452. Not sure why that's getting picked up. I've opened an issue at #73873 as this shouldn't be happening. I'm guessing if you rebase against a recent |
c9808bf
to
b77f907
Compare
thank you @boomanaiden154 for the analysis. clang-format check passed after rebase. However, there is new error:
@boomanaiden154 Do you have any idea about this error? Thank you |
No, I don't. As long as your tests pass locally, I wouldn't worry too much about the Buildkite failure. In a couple days the infrastructure for that should be getting migrated to Github actions now that Phabricator CI support is going away, so there's not going to be a lot of effort put into fixing these sorts of things on the Buildkite site. |
b77f907
to
694ec02
Compare
Thank you. |
694ec02
to
aa5e726
Compare
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.
LGTM
No description provided.