This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Minimal FDE


Hello,
Assuming executables are manipulated by splitting and resizing of
functions.
Here is a simplified case:
------------ before ---------
func1
-------
func2
------------ after -----------
func1_1
br func1_2
----------
func2
----------
func1_2
----------

Exception handling poses a problem. If func1 is referred in the .eh_frame,
we need to resize its FDE range to the size of func1_1, and create is new
FDE for func1_2.

Considering FDE formation, it consists of a header (size, CIE pointer, and
function address and size), followed by a sequence of (DWARF) instructions.

How critical are these instructions to the unwinding process?
Is  there some minimal/simplified set of instructions that will allow
exceptions to be properly caught?

Regards,
Yaakov



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]