llvm-project

Commit Graph

Author	SHA1	Message	Date
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
Rafael Espindola	0ac5075f31	Drop the "eh_" from eh_func_begin and eh_func_end. They will be used for more than eh tables. llvm-svn: 231185	2015-03-04 00:27:43 +00:00
Rafael Espindola	629cdbae94	Centralize handling of the eh_begin and eh_end labels. This removes a bit of duplicated code and more importantly, remembers the labels so that they don't need to be looked up by name. This in turn allows for any name to be used and avoids a crash if the name we wanted was already taken. llvm-svn: 230772	2015-02-27 18:18:39 +00:00

Author

SHA1

Message

Date

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

Rafael Espindola

0ac5075f31

Drop the "eh_" from eh_func_begin and eh_func_end.

They will be used for more than eh tables.

llvm-svn: 231185

2015-03-04 00:27:43 +00:00

Rafael Espindola

629cdbae94

Centralize handling of the eh_begin and eh_end labels.

This removes a bit of duplicated code and more importantly, remembers the
labels so that they don't need to be looked up by name.

This in turn allows for any name to be used and avoids a crash if the name
we wanted was already taken.

llvm-svn: 230772

2015-02-27 18:18:39 +00:00

3 Commits