diff options
| author | Bill Wendling <isanbard@gmail.com> | 2013-03-21 23:30:12 +0000 |
|---|---|---|
| committer | Bill Wendling <isanbard@gmail.com> | 2013-03-21 23:30:12 +0000 |
| commit | d9ff8c83d137586d8c06f98bdf8adbf0d1fa79ca (patch) | |
| tree | 9eb3d25e40b034c95a8d90282c7be11e010510e7 /utils/TableGen/TableGen.cpp | |
| parent | 3ea1b064a0b9c3d161b0f77a9e957970f98907ab (diff) | |
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
Diffstat (limited to 'utils/TableGen/TableGen.cpp')
0 files changed, 0 insertions, 0 deletions