This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Dynamically generated code and DWARF exception handling
On Wed, May 03, 2006 at 10:14:23AM +0100, Andrew Haley wrote:
> Adding an entry point to register debug info should not be a big deal.
> We're going to need it for gcj when we add a JIT.
>
> Another interesting possibility would be runtime extensions to
> MD_FALLBACK_FRAME_STATE_FOR. That would be more flexible because it
> would allow us to use a JIT's native debug info, not just DWARF.
Well, MD_FALLBACK_FRAME_STATE_FOR is used solely in the DWARF2/3 unwinder.
Furthermore, exposing the changing internals of the unwinder sounds
like very bad idea, just registering generated .eh_frame with the unwinder
sounds much better.
Alternatively, if the generated code always calls at most a handful
controlled entry points, one could write sophisticated unwind info for those
entry points that would not only unwind through that entry point routine,
but also through the generated code above it and you wouldn't need any
unwinder changes at all.
Jakub