public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2524] c++: top level bind when rewriting coroutines [PR106188]
Date: Wed,  7 Sep 2022 14:47:55 +0000 (GMT)	[thread overview]
Message-ID: <20220907144755.A36F63858403@sourceware.org> (raw)

https://gcc.gnu.org/g:a961ad1b13b9c294d4565344912b8e35ba71b369

commit r13-2524-ga961ad1b13b9c294d4565344912b8e35ba71b369
Author: Arsen Arsenović <arsen@aarsen.me>
Date:   Sun Sep 4 21:04:23 2022 +0200

    c++: top level bind when rewriting coroutines [PR106188]
    
    In the edge case of a coroutine not containing any locals, the ifcd/switch
    temporaries would get added to the coroutine frame, corrupting its
    layout. To prevent this, we can make sure there is always a BIND_EXPR at
    the top of the function body, and thus, always a place for our new
    temporaries to go without interfering with the coroutine frame.
    
    PR c++/106188 - Incorrect frame layout after transforming conditional statement without top-level bind expression
    PR c++/106713 - if (co_await ...) crashes with a jump to ud2
    
            PR c++/106188
            PR c++/106713
    
    gcc/cp/ChangeLog:
    
            * coroutines.cc (coro_rewrite_function_body): Ensure we have a
            BIND_EXPR wrapping the function body.
    
    gcc/testsuite/ChangeLog:
    
            * g++.dg/coroutines/pr106188.C: New test.
    
    Signed-off-by: Arsen Arsenović <arsen@aarsen.me>

Diff:
---
 gcc/cp/coroutines.cc                       |  9 ++++++++
 gcc/testsuite/g++.dg/coroutines/pr106188.C | 34 ++++++++++++++++++++++++++++++
 2 files changed, 43 insertions(+)

diff --git a/gcc/cp/coroutines.cc b/gcc/cp/coroutines.cc
index edb3b706ddc..eca01abcb7a 100644
--- a/gcc/cp/coroutines.cc
+++ b/gcc/cp/coroutines.cc
@@ -4095,6 +4095,15 @@ coro_rewrite_function_body (location_t fn_start, tree fnbody, tree orig,
       BLOCK_SUPERCONTEXT (replace_blk) = top_block;
       BLOCK_SUBBLOCKS (top_block) = replace_blk;
     }
+  else
+    {
+      /* We are missing a top level BIND_EXPR. We need one to ensure that we
+	 don't shuffle around the coroutine frame and corrupt it.  */
+      tree bind_wrap = build3_loc (fn_start, BIND_EXPR, void_type_node,
+				   NULL, NULL, NULL);
+      BIND_EXPR_BODY (bind_wrap) = fnbody;
+      fnbody = bind_wrap;
+    }
 
   /* Wrap the function body in a try {} catch (...) {} block, if exceptions
      are enabled.  */
diff --git a/gcc/testsuite/g++.dg/coroutines/pr106188.C b/gcc/testsuite/g++.dg/coroutines/pr106188.C
new file mode 100644
index 00000000000..9db3778d079
--- /dev/null
+++ b/gcc/testsuite/g++.dg/coroutines/pr106188.C
@@ -0,0 +1,34 @@
+// { dg-do run { target c++20 } }
+// test case from pr106188, w/o workaround
+#include <coroutine>
+
+struct task {
+  struct promise_type {
+    task get_return_object() { return task{}; }
+    void return_void() {}
+    void unhandled_exception() {}
+    auto initial_suspend() noexcept { return std::suspend_never{}; }
+    auto final_suspend() noexcept { return std::suspend_never{}; }
+  };
+};
+
+struct suspend_and_resume {
+  bool await_ready() const { return false; }
+  void await_suspend(std::coroutine_handle<> h) { h.resume(); }
+  void await_resume() {}
+};
+
+task f() {
+  if (co_await suspend_and_resume{}, false) {}
+}
+
+task g() {
+  switch (co_await suspend_and_resume{}, 0) {
+    default: break;
+  }
+}
+
+int main() {
+  f();
+  g();
+}

                 reply	other threads:[~2022-09-07 14:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220907144755.A36F63858403@sourceware.org \
    --to=jason@gcc.gnu.org \
    --cc=gcc-cvs@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).