From: "Arsen Arsenović" <arsen@aarsen.me>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] coroutines: Ensure there's a top level bind when rewriting [PR106188]
Date: Wed, 07 Sep 2022 17:28:01 +0200 [thread overview]
Message-ID: <8912987.C8XvtMWS5z@bstg> (raw)
In-Reply-To: <fe7c5b3c-5772-66dd-c004-061675665a6f@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
Hi,
On Wednesday, 7 September 2022 17:13:03 CEST Jason Merrill wrote:
> Applied with some minor tweaks, described below.
>
> Thanks!
Got it, and noted the changes and rationale you provided
Thank you!
--
Arsen Arsenović
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
prev parent reply other threads:[~2022-09-07 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 20:57 [PATCH] coroutines: Wrap awaiting if/swich in a BIND_EXPR, if needed [PR106188] Arsen Arsenović
2022-09-04 10:35 ` Iain Sandoe
2022-09-04 19:04 ` [PATCH v2] coroutines: Ensure there's a top level bind when rewriting [PR106188] Arsen Arsenović
2022-09-04 22:09 ` Iain Sandoe
2022-09-05 11:15 ` Arsen Arsenović
2022-09-07 15:13 ` Jason Merrill
2022-09-07 15:28 ` Arsen Arsenović [this message]
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=8912987.C8XvtMWS5z@bstg \
--to=arsen@aarsen.me \
--cc=gcc-patches@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).