public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bin.Cheng" <amker.cheng@gmail.com>
To: "bin.cheng" <bin.cheng@linux.alibaba.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Iain Sandoe <iain@sandoe.co.uk>, 	Nathan Sidwell <nathan@acm.org>
Subject: Re: [PATCH Coroutines]Insert the default return_void call at correct position
Date: Mon, 10 Feb 2020 08:49:00 -0000	[thread overview]
Message-ID: <CAHFci2-VFSkU83eKFqg0xAoN=xcAX+xB2NdGkdOy8C6hSOFN1A@mail.gmail.com> (raw)
In-Reply-To: <2f70c962-124a-4fb5-9f0a-ce1ee9d38a54.bin.cheng@linux.alibaba.com>

Ping.

Thanks,
bin

On Mon, Feb 3, 2020 at 1:55 PM bin.cheng <bin.cheng@linux.alibaba.com> wrote:
>
> Hi,
>
> Exception in coroutine is not correctly handled because the default
> return_void call is now inserted before the finish suspend point,
> rather than at the end of the original coroutine body.  This patch
> fixes the issue by generating following code:
>   co_await promise.initial_suspend();
>   try {
>     // The original coroutine body
>
>     promise.return_void(); // The default return_void call.
>   } catch (...) {
>     promise.unhandled_exception();
>   }
>   final_suspend:
>   // ...
>
> Bootstrap and test on x86_64.  Is it OK?
>
> Thanks,
> bin
>
> gcc/cp
> 2020-02-03  Bin Cheng  <bin.cheng@linux.alibaba.com>
>
>         * coroutines.cc (build_actor_fn): Factor out code inserting the
>         default return_void call to...
>         (morph_fn_to_coro): ...here, also hoist local var declarations.
>
> gcc/testsuite
> 2020-02-03  Bin Cheng  <bin.cheng@linux.alibaba.com>
>
>         * g++.dg/coroutines/torture/co-ret-15-default-return_void.C: New.

  reply	other threads:[~2020-02-10  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  5:55 bin.cheng
2020-02-10  8:49 ` Bin.Cheng [this message]
2020-02-10 11:55   ` Iain Sandoe
2020-02-13 18:20     ` Iain Sandoe
2020-02-27 12:08 ` Nathan Sidwell

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='CAHFci2-VFSkU83eKFqg0xAoN=xcAX+xB2NdGkdOy8C6hSOFN1A@mail.gmail.com' \
    --to=amker.cheng@gmail.com \
    --cc=bin.cheng@linux.alibaba.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=nathan@acm.org \
    /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).