This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Compiling with gcc-4.0.0 and -fno-exceptions
- From: Paolo Carlini <pcarlini at suse dot de>
- To: Daniel Kegel <dank at kegel dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Tue, 07 Jun 2005 10:43:21 +0200
- Subject: Re: Compiling with gcc-4.0.0 and -fno-exceptions
- References: <42A531E1.7060109@kegel.com>
Daniel Kegel wrote:
> If that sounds about right, I can submit a bug report / patch
> for the things I've run into.
I see. That's annoying.
When -fno-exceptions, 'try' becomes 'if (true)' and 'catch(X)' becomes
'if (false)': my guess would be that a sufficiently smart compiler
should be able to figure out statically that the no-return branch is
never taken. Can you possibly check whether mainline and 4.0.1 pre are
also affected? For sure we had quite a few of those spurious warnings in
Bugzilla and most have been fixed. I would suggest trying to figure
which is the current situation in Bugzilla, 4.0.1 pre, and mainline (I
can also do that, of course, but would appreciate a stand-alone snippet
from your work) and then take the appropriate action. Changing the
library seems not an option.
Paolo.