This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: CLEANUP_POINT_EXPR/WITH_CLEANUP_EXPR vs TRY_CATCH_EXPR
- To: kenner at vlsi1 dot ultra dot nyu dot edu
- Subject: Re: CLEANUP_POINT_EXPR/WITH_CLEANUP_EXPR vs TRY_CATCH_EXPR
- From: Richard Stallman <rms at gnu dot org>
- Date: Mon, 21 Dec 1998 06:59:10 -0700 (MST)
- CC: egcs at cygnus dot com, gcc2 at gnu dot org
- References: <9812201027.AA16766@vlsi1.ultra.nyu.edu>
- Reply-to: rms at gnu dot org
No question about that! The issue here was front ends that *do not* use
the EH tree codes.
Why does the question affect these front ends? It can only be
because GCC output code, in certain cases, to support error handling,
even in functions that don't use error handling constructs.
Why would GCC do that? Surely because that code is needed to make
these functions interoperate properly with the use of EH in other functions.
In such a case, GCC should do that for all languages, even languages
that have no EH constructs of their own. Because those languages
should interoperate properly with the languages that do have EH constructs.