There are times when the landing pad won't have a call to 'eh.selector' in
authorBill Wendling <isanbard@gmail.com>
Thu, 3 Mar 2011 23:14:05 +0000 (23:14 +0000)
committerBill Wendling <isanbard@gmail.com>
Thu, 3 Mar 2011 23:14:05 +0000 (23:14 +0000)
commite7147dba733c95aec215f5576539b07f11636ff3
treeccfbcf33dbcc4b9ceb7797c38dbca6a5989ababc
parent58f04fd22a3bbbb5b2620b6feecc36cf1b878dbd
There are times when the landing pad won't have a call to 'eh.selector' in
it. It's been assumed up til now that it would be in its immediate
successor. However, this isn't necessarily the case. It could be in one of its
successor's successors.

Modify the code to more thoroughly check for an 'eh.selector' call in
successors. It only looks at a successor if we get there as a result of an
unconditional branch.

Testcase ObjC/exceptions-4.m in r126968.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@126969 91177308-0d34-0410-b5e6-96231b3b80d8
include/llvm/CodeGen/FunctionLoweringInfo.h
lib/CodeGen/SelectionDAG/FunctionLoweringInfo.cpp