[Analysis][LV] Handle FMinNum/FMaxNum in RecurrenceDescriptor::getOpcode #152794
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.
Modify
RecurrenceDescriptor::getOpcodeto handleRecurKind::FMinNumandRecurKind::FMaxNumby returningInstruction::FCmp, matchingFMin/FMax.Without these cases, querying the opcode for minNum/maxNum reductions can hit
llvm_unreachablein code that inspects the recurrence kind. Also addedIVDescriptorsTest.GetOpcodeForFMinMaxNum(gtest) to verify the mapping.