public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95003] New: coroutines: Wrong code for some reference capture cases.
Date: Fri, 08 May 2020 09:41:26 +0000	[thread overview]
Message-ID: <bug-95003-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95003

            Bug ID: 95003
           Summary: coroutines: Wrong code for some reference capture
                    cases.
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: iains at gcc dot gnu.org
  Target Milestone: ---

Created attachment 48479
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48479&action=edit
patch under test

The following code does not work correctly, the loop is executed but the loop
body is discarded during gimplifcation.

There are several places where we insert bind expressions while making the
coroutine AST transforms.  These should be marked as having side-effects where
relevant, which had been omitted - leading to the fail - since, at least in
some cases, such bind expressions are dropped during gimplification.


struct Awaitable {
  int v;
  Awaitable (int _v) : v(_v) {}
  bool await_ready() { return false; }
  void await_suspend(std::coroutine_handle<coro1::promise_type>) {}
  int await_resume() { return v; }
  auto operator co_await() { return *this; }
};

coro1
my_coro
(int x)
{
  int sum = 0;
  for (unsigned i = 0; i < 100; ++i) {
    sum += co_await Awaitable{x+1};
  }
  co_return sum;
}

             reply	other threads:[~2020-05-08  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08  9:41 iains at gcc dot gnu.org [this message]
2020-05-08  9:42 ` [Bug c++/95003] " iains at gcc dot gnu.org
2020-05-08 19:47 ` cvs-commit at gcc dot gnu.org
2020-05-09 10:43 ` iains at gcc dot gnu.org
2020-05-10 15:56 ` cvs-commit at gcc dot gnu.org
2020-05-13 16:56 ` iains at gcc dot gnu.org

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=bug-95003-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).