This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs and exceptions
- To: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Subject: Re: egcs and exceptions
- From: Jason Merrill <jason at cygnus dot com>
- Date: 02 Nov 1998 22:41:53 -0800
- Cc: egcs at cygnus dot com
- References: <Pine.A32.3.91.981022102148.50968A-100000@ieva06.lanet.lv> <orpvbbt1mq.fsf.cygnus.egcs@araguaia.dcc.unicamp.br> <u9vhl1j9e9.fsf@yorick.cygnus.com> <orhfwkc3ao.fsf@araguaia.dcc.unicamp.br>
>>>>> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
> On Oct 31, 1998, Jason Merrill <jason@cygnus.com> wrote:
>>>>>>> Alexandre Oliva <oliva@dcc.unicamp.br> writes:
>>> Maybe you have to build libgcc.a and libstdc++.a with this option
>>> enabled.
>> Yes. If you want to use sjlj, it makes more sense to change
>> the default for exceptions_via_longjmp in except.c and rebuild the
>> compiler, rather than trying to consistently pass the flag. This is true
>> for other ABI flags, as well.
> But the doubt is: must you do that, or can you just compile and link
> foo.cc with -fsjlj-exceptions on Solaris and it will work?
It may work, but not reliably.
Jason