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
..
BitcodeReader.cpp	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
BitReader.cpp	Return a unique_ptr from getLazyBitcodeModule and parseBitcodeFile. NFC.	2015-06-16 22:27:55 +00:00
BitstreamReader.cpp	[BitstreamReader] Make sure the Array operand type is an encoding	2015-05-27 00:48:43 +00:00
CMakeLists.txt	Use ADDITIONAL_HEADER_DIRS in all LLVM CMake projects.	2015-02-11 03:28:02 +00:00
LLVMBuild.txt
Makefile