This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Bug in egcs 1.1 -fno-rtti + exception = segfault
- To: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Subject: Re: Bug in egcs 1.1 -fno-rtti + exception = segfault
- From: Marco Manfai Yu <yumf at ultimatech dot com>
- Date: Mon, 26 Oct 1998 23:16:43 -0800
- cc: yumf at ultimatech dot com, egcs-bugs at cygnus dot com
How about the following?
1. Enable both exception handling and rtti if either is enabled
explicitly on the command line.
2. Disable both if either is disabled explicity on the command
line.
3. Produce a warning and turn on both if conflicting flags are
given on the command line.
4. Enable both by default.
Marco Yu
yumf@ultimatech.com
> Marco Manfai Yu <yumf@ultimatech.com> writes:
>
> > Basically the code throws one of the standard exceptions. When
> > compiled with -fno-rtti the code segfaults in __is_pointer().
>
> The runtime needs RTTI in order to check exception types. IMO, you
> shouldn't be able to disable rtti without disabling exceptions too.
> We should certainly emit a warning in this case, but I'm unsure
> whether we should re-enable rtti if exceptions are enabled, or
> implicitly disable exception handling too, so that any
> exception-handling construct would be flagged as an error. What do
> others think?
>
> --
> 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