[cfe-dev] CFG temporary objects destructors

[Zhongxing Xu]

When the binary operator is logical operator, why we need to replicate the
control flow when adding the dtors in LHS and RHS? Could we just add the
dtor right after where the LHS and RHS are evaluated?

That is, for code

A && B

we generate CFG like this:

A && B
~A()
|      \
|       B
|       ~B()
|        |
A && B

Since in logical binary operator, we only need the boolean value. The
temporary object can be destroyed right after it is evaluated.

2010/10/18 Marcin Świderski <marcin.sfider at gmail.com>

> Hi
>
> I'm currently working on modeling destructors of temporary objects in CFG.
> I've attached patch with prototype implementation and some tests.
>
> After some thinking I've decided to add additional step with forward
> traversing of AST for every CXXExprWithTemporaries node. During this step
> destructors are added to CFG for every CXXBindTemporaryExpr (with special
> case for binding const reference to temporary). However I have a problem
> with branching for destructors that have to be called conditionaly. Blocks
> structure that is constructed is fine, but I don't know what to use for
> terminator of block initiating the branch and for first element in block
> closing the branch (I didn't check this yet, but I think that it could be
> used during backward analysis). Could I use fake if/else statement for this?
> Similar solution is used to make every declaration into separate statement.
>
> - Marcin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20101022/5e6ac1fc/attachment.html>