[SelectionDAG] Fix the assertion failure in Release build after #91747 #93416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #91747, we changed the SDNode from
X86ISD::SUB
(FROM) toX86ISD::CCMP
(TO) in the DAGCombine. The value type of X86ISD::SUB can bei8, i32
while the value type of X86ISD::CCMP isi32
.That means the
SDValue(FROM, 0)
is unused and may be removed. However,transferDbgValues
assumes the value is not null, which is called byReplaceAllUsesWith(SDNode *, const SDValue *)
. So we need to check if the value has any use before calling the function.Note: We already have same check in
ReplaceAllUsesWith(SDNode *, SDNode *)
.This fix the error
for tests
llvm/test/CodeGen/X86/apx/ccmp.ll
llvm/test/CodeGen/X86/apx/ctest.ll
in Release build when LLVM_ENABLE_ASSERTIONS is on.