From: Richard Sandiford <richard.sandiford@arm.com>
To: Philipp Rimmele via Gcc <gcc@gcc.gnu.org>
Cc: Philipp Rimmele <ph_rimmele@hotmail.com>
Subject: Re: try_finally_expr in must_not_throw_expr
Date: Tue, 02 Aug 2022 13:23:08 +0100 [thread overview]
Message-ID: <mpt5yjarg0j.fsf@arm.com> (raw)
In-Reply-To: <PRAP195MB1483F5F02BDBFC7E70304365FF9B9@PRAP195MB1483.EURP195.PROD.OUTLOOK.COM> (Philipp Rimmele via Gcc's message of "Sun, 31 Jul 2022 14:25:35 +0000")
Philipp Rimmele via Gcc <gcc@gcc.gnu.org> writes:
> Hi,
>
> i'm developing a GCC-Plugin. And i don't understand why there is a "try_finally_expr" in a must_not_throw-Area in my AST. It happens in the destructors.
> Here is my AST:
> function_decl Exception::__dt_base
> 1: must_not_throw_expr(->void_type{void})[42]
> 0: statement_list(->void_type{void})
> 0: bind_expr(->void_type{void})[42]
> 1: statement_list(->void_type{void})
> 0: cleanup_point_expr(->void_type{void})[42]
> 0: expr_stmt(->void_type{void})
> 0: convert_expr(->void_type{void})
> 0: modify_expr(->pointer_type->pointer_type{__vtbl_ptr_type}->function_type->integer_type{int})
> 0: component_ref(->pointer_type->pointer_type{__vtbl_ptr_type}->function_type->integer_type{int})
> 0: indirect_ref(->record_type{Exception})
> 0: nop_expr(->pointer_type->record_type{Exception})
> 0: parm_decl(->pointer_type->record_type{Exception}) : this
> 1: field_decl(->pointer_type->pointer_type{__vtbl_ptr_type}->function_type->integer_type{int})
> 1: pointer_plus_expr(->pointer_type->pointer_type{__vtbl_ptr_type}->function_type->integer_type{int})
> 0: addr_expr(->pointer_type->pointer_type{__vtbl_ptr_type}->function_type->integer_type{int})
> 0: var_decl(->array_type->pointer_type{__vtbl_ptr_type}->function_type->integer_type{int}) : _ZTV9Exception
> 1: integer_cst : 16 : 1
> 0: try_finally(->void_type{void})[42]
> 0: statement_list(->void_type{void})
> 1: modify_expr(->void_type{void})
> 0: indirect_ref(->record_type)
> 0: nop_expr(->reference_type->record_type)
> 0: parm_decl(->pointer_type->record_type{Exception}) : this
> 1: constructor(->record_type)
> 2: block
> 0: label_expr(->void_type{void})[42]
> 0: label_decl(->void_type{void}) : <unnamed>
>
> What is the reason for this? There should no Exception be thrown, so why handle it with a try_finally-Expression? I'm currently using GCC-8.2.0.
> I would be realy glad if you could answer me this question. And if you can give me some examples, where the try_finally-expression is also used, it would be realy helpfull.
I'm not an expert on this by any means, but since no-one else has
replied yet... I suspect it's simpler to use try_finally whenever
something needs to be run at the end of a scope, regardless of whether
the scope ends through fallthrough, breaking, continuing, or exceptions.
To put it another way: try_finally at this stage doesn't guarantee
that exception handling will actually be needed. For example:
try
{
int i = 1;
int j = 2;
if (i == j)
foo ();
}
finally ...
starts out with a potentially-throwing call to foo, but it (and the
possibility of an exception) will get optimised away later. It probably
didn't seem worthwhile having the frontend do a similar but separate
analysis of whether statements might throw.
Thanks,
Richard
prev parent reply other threads:[~2022-08-02 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 14:25 Philipp Rimmele
2022-08-02 12:23 ` Richard Sandiford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mpt5yjarg0j.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc@gcc.gnu.org \
--cc=ph_rimmele@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).