David Majnemer cc714e2142 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 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@239940 91177308-0d34-0410-b5e6-96231b3b80d8		2015-06-17 20:52:32 +00:00
..
AddressSanitizer	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
BoundsChecking	Add a bunch of CHECK missing colons in tests. NFC.	2015-03-14 01:43:57 +00:00
DataFlowSanitizer	IR: Give 'DI' prefix to debug info metadata	2015-04-29 16:38:44 +00:00
InstrProfiling	Final fix for PR 23499 and IR test case.	2015-05-27 19:34:01 +00:00
MemorySanitizer	When checking msan.module_ctor, use CHECK-LABEL instead of CHECK	2015-05-07 21:47:25 +00:00
SanitizerCoverage	IR: Give 'DI' prefix to debug info metadata	2015-04-29 16:38:44 +00:00
ThreadSanitizer	TSan: Use createSanitizerCtor to create ctor, and call __tsan_init	2015-05-07 21:41:23 +00:00