This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH RFA: Improve documentation of GIMPLE exception handling constructs


On Sun, Jul 10, 2005 at 10:27:56PM -0700, Ian Lance Taylor wrote:
> +@code{TRY_FINALLY_EXPR} has two operands, both of which are a sequence
> +of statements to execute.  The first sequence is executed.  When it
> +completes, however it does, the second sequence is executed.
> +
> +The first sequence may complete in the following ways:
> +
> +@enumerate
> +
> +@item Execute the last statement in the sequence and fall off the
> +end.
> +
> +@item Execute a goto statement (@code{GOTO_EXPR}).
> +
> +@item Execute a return statement (@code{RETURN_EXPR}).
> +
> +@item Throw an exception.  This is currently not explicitly represented in
> +GIMPLE.

If we're going to improve this, we might as well mention that we do not
execute the finally block when the try block is exited via setjmp, 
non-local-goto or computed goto.  So the GOTO_EXPR statement is only
correct when the operand is a label.

Otherwise it looks good.


r~


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]