llvm-6502/lib/Transforms
Bill Wendling d9ff8c83d1 Always forward 'resume' instructions to the outter landing pad.
How did this ever work?

Basically, if you have a function that's inlined into the caller, it may not
have any 'call' instructions, but any 'resume' instructions it may have should
still be forwarded to the outer (caller's) landing pad. This requires that all
of the 'landingpad' instructions in the callee have their clauses merged with
the caller's outer 'landingpad' instruction (hence the bit of ugly code in the
`forwardResume' method).

Testcase in a follow commit to the test-suite repository.

<rdar://problem/13360379> & PR15555


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177680 91177308-0d34-0410-b5e6-96231b3b80d8
2013-03-21 23:30:12 +00:00
..
Hello
InstCombine Perform factorization as a last resort of unsafe fadd/fsub simplification. 2013-03-14 18:08:26 +00:00
Instrumentation [msan] Add an option to disable poisoning of shadow for undef values. 2013-03-21 09:38:26 +00:00
IPO Move library call prototype attribute inference to functionattrs 2013-03-21 00:55:59 +00:00
ObjCARC Fixed a careless mistake. 2013-02-23 00:31:32 +00:00
Scalar [SROA] Prefix names using a custom IRBuilder inserter. 2013-03-21 09:52:18 +00:00
Utils Always forward 'resume' instructions to the outter landing pad. 2013-03-21 23:30:12 +00:00
Vectorize LoopVectorize: Invert case when we use a vector cmp value to query select cost 2013-03-14 18:54:36 +00:00
CMakeLists.txt
LLVMBuild.txt
Makefile