From: Yaakov Yaari <YAARI@il.ibm.com>
To: gcc@gcc.gnu.org
Subject: Minimal FDE
Date: Mon, 30 Aug 2004 20:03:00 -0000 [thread overview]
Message-ID: <OF80E0A6B6.5145BEA0-ONC2256F00.00579E78-C2256F00.00665F26@il.ibm.com> (raw)
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
next reply other threads:[~2004-08-30 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 20:03 Yaakov Yaari [this message]
2004-08-30 20:57 ` Richard Henderson
2004-09-01 4:22 ` Alan Modra
2004-09-01 6:51 ` Yaakov Yaari
2004-09-01 7:26 ` Alan Modra
2004-09-01 7:59 ` Yaakov Yaari
2004-09-01 8:27 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF80E0A6B6.5145BEA0-ONC2256F00.00579E78-C2256F00.00665F26@il.ibm.com \
--to=yaari@il.ibm.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).