This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs and exceptions
- To: Andris Pavenis <pavenis at lanet dot lv>
- Subject: Re: egcs and exceptions
- From: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Date: 29 Oct 1998 21:00:13 -200
- Cc: djgpp-workers at delorie dot com, egcs at cygnus dot com
- References: <Pine.A32.3.91.981022102148.50968A-100000@ieva06.lanet.lv>
Andris Pavenis <pavenis@lanet.lv> writes:
> with -fsjlj-exceptions : I was not able to get exceptions working
> for both Linux and DJGPP and with stable release (egcs-1.1)
> So it's seems that -fsjlj-exceptions is broken with egcs-1.1
> and later snapshots
Maybe you have to build libgcc.a and libstdc++.a with this option
enabled. At least that's my reading from gcc/except.c:
There are two major codegen options for exception handling. The
flag -fsjlj-exceptions can be used to select the setjmp/longjmp
approach, which is the default. -fno-sjlj-exceptions can be used to
get the PC range table approach. While this is a compile time
flag, an entire application must be compiled with the same codegen
option.
Of course one may argue that libgcc has nothing to do with `the entire
application', and I'm not really sure you must really choose sjlj at
build time, but if you have spare CPU cycles to try that, it would be
nice to know...
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:oliva@gnu.org mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil