This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: throwing exception when new fails
- To: egcs at cygnus dot com, nathan at acm dot org
- Subject: Re: throwing exception when new fails
- From: mrs at wrs dot com (Mike Stump)
- Date: Wed, 21 Oct 1998 11:52:20 -0700
> Date: Tue, 20 Oct 1998 19:07:06 +0100
> From: Nathan Sidwell <nathan@acm.org>
> To: egcs@cygnus.com
> Anyway, I've been figuring out how to fix this.
Your plans sound good. I think you're on the right track. I not sure
what is best when it comes to the large mallow up front for the entire
table. It is there so that we can do a simple binary walk (fast) on
the data structure to look up EH related information during unwinding.
Preallocate at init time maybe? Or maybe have a fallback that can
walk unsorted chains if malloc fails. Anyone else have any ideas on
good solutions? I think we've thought about named sections, and
having the linker combine them, so in the end we wind up enough room
for the data, but the one has to do something tricky for dyn loaded
code and shared libraries.
Thanks for thinking about these issue, and we all look forward to any
improvement you can bring to the code.