This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: throwing exception when new fails
- To: mrs at wrs dot com
- Subject: Re: throwing exception when new fails
- From: Martin von Loewis <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Thu, 22 Oct 1998 23:19:16 +0100
- CC: egcs at cygnus dot com, nathan at acm dot org
- References: <199810211852.LAA21692@kankakee.wrs.com>
> 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.
I'd like to emphasize this option. Even if it works only with GNU ld,
there is still value in having the linker sort the FDEs, instead of
sorting at run time. The linker could set a bit somewhere to indicate
that it did the sorting, which would show drastic improvements in
memory consumtion and execution speed for large binaries.
All we need is a volunteer. :-)
Regards,
Martin