The function SplitCriticalEdge (called by SplitEdge) can return a nullptr in cases where the edge is a critical. SplitEdge uses SplitCriticalEdge assuming it can always split all critical edges, which is an incorrect assumption.
The three cases where the function SplitCriticalEdge will return a nullptr is:
- DestBB is an exception block
- Options.IgnoreUnreachableDests is set to true and isa(DestBB->getFirstNonPHIOrDbgOrLifetime()) is not equal to a nullptr
- LoopSimplify form must be preserved (Options.PreserveLoopSimplify is true) and it cannot be maintained for a loop due to indirect branches
For each of these situations they are handled in the following way:
- Modified the function ehAwareSplitEdge originally from llvm/lib/Transforms/Coroutines/CoroFrame.cpp to handle the cases when the DestBB is an exception block. This function is called directly in SplitEdge. SplitEdge does not call SplitCriticalEdge in this case
- Options.IgnoreUnreachableDests is set to false by default, so this situation does not apply.
- Return a nullptr in this situation since the SplitCriticalEdge also returned nullptr. Nothing we can do in this case.
clang-tidy: warning: invalid case style for function 'SplitKnownCriticalEdge' [readability-identifier-naming]
not useful