This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __throw and __sjthrow
- To: egcs at cygnus dot com, manush at litecom dot se
- Subject: Re: __throw and __sjthrow
- From: mrs at wrs dot com (Mike Stump)
- Date: Thu, 5 Mar 1998 15:33:33 -0800
> Date: Thu, 5 Mar 1998 19:58:54 +0100 (CET)
> From: Manush Dodunekov <manush@litecom.se>
> To: egcs@cygnus.com
> When I run nm on an executable compiled with egcs-1.0.1, I notice
> both __throw and __sjthrow. Isn't it supposed to use only one of
> the mechanisms on a given platform?
The idea is that you can default to -no-sjlj-exceptions, and compile
with -fsjlj-exceptions if you need them. To work completely, you will
need the c++ library multilibed. People that really need this, can
have it. libgcc was designed to not need multilibing on this point.