This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Consistently using __throw_* (was: Re: PATCH: Eliminate uses of "sleep"...)
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Paolo Carlini <pcarlini at suse dot de>
- Cc: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>, Mark Mitchell <mark at codesourcery dot com>, "'gcc-patches at gcc dot gnu dot org'" <gcc-patches at gcc dot gnu dot org>, libstdc++ <libstdc++ at gcc dot gnu dot org>, Benjamin Kosnik <bkoz at redhat dot com>
- Date: 05 Jan 2005 16:21:56 +0100
- Subject: Re: Consistently using __throw_* (was: Re: PATCH: Eliminate uses of "sleep"...)
- Organization: Integrable Solutions
- References: <41DBFF39.7000602@suse.de>
Paolo Carlini <pcarlini@suse.de> writes:
| > "__throw_exception_again;" should be used in place of "throw;" to rethrow
| > an active exception. With -fno-exceptions __throw_exception_again is
| > replaced with an empty string, which is not what's wanted.
|
| You are right, in my opinion, but let's not involve our release manager
| with our (v3) bugs... ;)
|
| I mean, some time ago I did an audit for this issue, and for a consistent
| fix we need to add a few functions to the set in functexcept.h.
| At least:
|
| __throw (which boils down to either throw or abort)
| __throw_symbol_error
| __throw_facet_error
| __throw_positioning_error
| __throw_fuzzy_logic
|
| and consistently use some already present, like
|
| __throw_overflow_error
| __throw_underflow_error
|
| If we agree, I can prepare a patch. Benjamin?
OK with me.