This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __register_frame_info and unwinding shared libraries
- From: Richard Henderson <rth at redhat dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 15 Feb 2005 09:41:22 -0800
- Subject: Re: __register_frame_info and unwinding shared libraries
- References: <16914.12531.871015.381228@cuddles.cambridge.redhat.com>
On Tue, Feb 15, 2005 at 05:27:15PM +0000, Andrew Haley wrote:
> So, now for my question: why do we not call __register_frame_info() or
> __register_frame_info_bases() ?
Because in the normal case for C/C++, folks don't use that many
exceptions. So delaying doing anything until it's needed is a win.
Obviously the normal case is different for Java.
> We'd avoid a great many trips through
> dl_iterate_phdr () and _Unwind_IteratePhdrCallback().
While I still like using dl_iterate_phdr instead of
__register_frame_info_bases for totally aesthetic reasons, there have
been changes made to the dl_iterate_phdr interface since the gcc support
was written that would allow the dl_iterate_phdr results to be cached.
r~