A completely different approach to EH runtime
Jeff Sturm
jsturm@one-point.com
Wed Feb 21 01:10:00 GMT 2001
On Tue, 20 Feb 2001, Zack Weinberg wrote:
> All executables linked with -fexceptions (whether or not that's the
> language default) get crteh.o thrown in right after crtbegin.o, and
> libeh.a at the very beginning of the library list.
Wouldn't you either have to force it to be the default on all frontends,
or break backward compatibility by requiring -fexceptions in some cases?
It's not unheard of to invoke a shared library that needs EH
from a C stub that doesn't. In fact that is what gcj does today.
> Therefore all the
> libraries bind to the copy of the eh routines in the executable.
How so? In my experience many (most?) shared object formats do not bind
libraries to global symbols, or even allow undefined symbols in a library
at link time. ELF is an exception.
Jeff
More information about the Gcc
mailing list