On Mon, 2011-11-21 at 14:58 -0800, Richard Henderson wrote:
> On 11/21/2011 01:58 PM, Torvald Riegel wrote:
> > On Mon, 2011-11-21 at 13:45 -0800, Richard Henderson wrote:
> >> On 11/21/2011 01:39 PM, Torvald Riegel wrote:
> >>> It still fails when combined
> >>> with transaction expressions (noexc
Here's the patch to add an argument to MUST_NOT_THROW_EXPR. You should
be able to just use build_must_not_throw_expr in the tm code.
Jason
commit 205ca057f90db6c30d1acd64ec796e7d301b3eb8
Author: Jason Merrill
Date: Tue Nov 22 10:19:03 2011 -0500
build_must
diff --git a/gcc/cp/cp-tree.
On 11/21/2011 01:58 PM, Torvald Riegel wrote:
> On Mon, 2011-11-21 at 13:45 -0800, Richard Henderson wrote:
>> On 11/21/2011 01:39 PM, Torvald Riegel wrote:
>>> It still fails when combined
>>> with transaction expressions (noexcept-4.C and noexcept-1.C) because
>>> gimplify_must_not_throw_expr() c
On Mon, 2011-11-21 at 13:45 -0800, Richard Henderson wrote:
> On 11/21/2011 01:39 PM, Torvald Riegel wrote:
> > It still fails when combined
> > with transaction expressions (noexcept-4.C and noexcept-1.C) because
> > gimplify_must_not_throw_expr() calls voidify_wrapper_expr() on a
> > MUST_NOT_THR
On 11/21/2011 01:39 PM, Torvald Riegel wrote:
> It still fails when combined
> with transaction expressions (noexcept-4.C and noexcept-1.C) because
> gimplify_must_not_throw_expr() calls voidify_wrapper_expr() on a
> MUST_NOT_THROW_EXPR which it doesn't know to be a wrapper. What's the
> cleanest
On Mon, 2011-11-21 at 12:30 -0800, Richard Henderson wrote:
> On 11/21/2011 12:27 PM, Torvald Riegel wrote:
> > voidify_wrapper_expr didn't handle MUST_NOT_THROW_EXPR before, but was
> > used by the C++ side gimplify function for MUST_NOT_THROW_EXPR. Handle
> > it like other wrappers which have th
On 11/21/2011 12:27 PM, Torvald Riegel wrote:
> voidify_wrapper_expr didn't handle MUST_NOT_THROW_EXPR before, but was
> used by the C++ side gimplify function for MUST_NOT_THROW_EXPR. Handle
> it like other wrappers which have the inner part in operand 0.
>
> OK for trunk?
Not ok. This is a c+
voidify_wrapper_expr didn't handle MUST_NOT_THROW_EXPR before, but was
used by the C++ side gimplify function for MUST_NOT_THROW_EXPR. Handle
it like other wrappers which have the inner part in operand 0.
OK for trunk?
commit 9cb965d2a5cf9ca6708ee85929784982253ded7a
Author: Torvald Riegel
Date: