292077072e
With the addition of the `willreturn` attribute, functions that may not return (e.g. due to an infinite loop) are well defined, if they are not marked as `willreturn`. This patch updates `wouldInstructionBeTriviallyDead` to not consider calls that may not return as dead. This patch still provides an escape hatch for intrinsics, which are still assumed as willreturn unconditionally. It will be removed once all intrinsics definitions have been reviewed and updated. Reviewed By: jdoerfert Differential Revision: https://reviews.llvm.org/D94106
29 lines
793 B
LLVM
29 lines
793 B
LLVM
; RUN: opt < %s -inline -reassociate -S | FileCheck %s
|
|
|
|
; This test case exposed a bug in reassociate where EraseInst's
|
|
; removal of a dead call wasn't recognized as changing the IR.
|
|
; So when runOnFunction propagated the "made changes" upwards
|
|
; to the CallGraphSCCPass it signalled that no changes had been
|
|
; made, so CallGraphSCCPass assumed that the old CallGraph,
|
|
; as known by that pass manager, still was up-to-date.
|
|
;
|
|
; This was detected as an assert when trying to remove the
|
|
; no longer used function 'bar' (due to incorrect reference
|
|
; count in the CallGraph).
|
|
|
|
define void @foo() {
|
|
; CHECK-LABEL: @foo(
|
|
; CHECK-NEXT: entry:
|
|
; CHECK-NEXT: ret void
|
|
entry:
|
|
call void @bar()
|
|
ret void
|
|
}
|
|
|
|
define internal void @bar() noinline nounwind readnone willreturn {
|
|
entry:
|
|
ret void
|
|
}
|
|
|
|
|