llvm-project/llvm/test/LTO/X86
David Majnemer 7fddeccb8b Move the personality function from LandingPadInst to Function
The personality routine currently lives in the LandingPadInst.

This isn't desirable because:
- All LandingPadInsts in the same function must have the same
  personality routine.  This means that each LandingPadInst beyond the
  first has an operand which produces no additional information.

- There is ongoing work to introduce EH IR constructs other than
  LandingPadInst.  Moving the personality routine off of any one
  particular Instruction and onto the parent function seems a lot better
  than have N different places a personality function can sneak onto an
  exceptional function.

Differential Revision: http://reviews.llvm.org/D10429

llvm-svn: 239940
2015-06-17 20:52:32 +00:00
..
Inputs
attrs.ll
bcsection.ll
cfi_endproc.ll libLTO, llvm-lto, gold: Introduce flag for controlling optimization level. 2015-03-19 22:01:00 +00:00
current-section.ll
diagnostic-handler-remarks.ll
invalid.ll
keep-used-puts-during-instcombine.ll [opaque pointer type] Add textual IR support for explicit type parameter to the call instruction 2015-04-16 23:24:18 +00:00
linkonce_odr_func.ll Move the personality function from LandingPadInst to Function 2015-06-17 20:52:32 +00:00
list-symbols.ll
lit.local.cfg
no-undefined-puts-when-implemented.ll [opaque pointer type] Add textual IR support for explicit type parameter to the call instruction 2015-04-16 23:24:18 +00:00
private-symbol.ll
runtime-library.ll
set-merged.ll [opaque pointer type] Add textual IR support for explicit type parameter to load instruction 2015-02-27 21:17:42 +00:00
symver-asm.ll
triple-init.ll