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++/94701] New: coroutines: Wrong code for structured bindings.
Date: Tue, 21 Apr 2020 20:14:28 +0000	[thread overview]
Message-ID: <bug-94701-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94701
           Summary: coroutines: Wrong code for structured bindings.
           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 48330
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48330&action=edit
patch under test

As reported by Michał Dominiak, the following code gets an incorrect answer -
this is because we fail to check for DECL_VALUE_EXPR in the handling for local
vars.

struct promise;

struct future
{
  using promise_type = promise;
};

struct promise
{
  template<typename... Args>
  promise (Args&... args) {}

  coro::suspend_never initial_suspend() { return {}; }
  coro::suspend_never final_suspend() { return {}; }

  future get_return_object() { return {}; }

  void return_value(int) {}
  void unhandled_exception() {}
};

#include <cassert>

struct pair
{
  int i;
};

pair 
something ()
{
  return { 1 };
}

future 
my_coro ()
{   
  auto ret = something ();
  assert(ret.i == 1);

  auto [ i ] = something ();
  assert(i == 1);

  co_return 1;
}

int main ()
{
  my_coro ();
}

             reply	other threads:[~2020-04-21 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 20:14 iains at gcc dot gnu.org [this message]
2020-04-21 20:15 ` [Bug c++/94701] " iains at gcc dot gnu.org
2020-04-27 22:58 ` cvs-commit at gcc dot gnu.org
2020-04-27 23:46 ` 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-94701-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).