public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Iain Sandoe <iain@sandoe.co.uk>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [C++ coroutines 2/6] Define builtins and internal functions.
Date: Sun, 17 Nov 2019 16:54:00 -0000	[thread overview]
Message-ID: <1c45bdc4-d3b0-430a-3bf0-f8571c2c88aa@redhat.com> (raw)
In-Reply-To: <B9BF0CEA-C9A7-4F63-91AC-24F87538177D@sandoe.co.uk>

On 11/17/19 3:24 AM, Iain Sandoe wrote:
> 
> This part of the patch series provides the builtin functions
> used by the standard library code and the internal functions
> used to implement lowering of the coroutine state machine.
> 
> gcc/ChangeLog:
> 
> 2019-11-17  Iain Sandoe  <iain@sandoe.co.uk>
> 
> 	* builtin-types.def (BT_FN_BOOL_PTR): New.
> 	(BT_FN_PTR_PTR_SIZE_BOOL): New.
> 	* builtins.def (DEF_COROUTINE_BUILTIN): New.
> 	* coroutine-builtins.def: New file.
> 	* internal-fn.c (expand_CO_FRAME): New.
> 	(expand_CO_YIELD): New.
> 	(expand_CO_SUSPN): New.
> 	(expand_CO_ACTOR): New.
> 	* internal-fn.def (CO_ACTOR): New.
> 	(CO_YIELD): New.
> 	(CO_SUSPN): New.
> 	(CO_FRAME): New.
This is OK as would be any minor adjustments you may ultimately need due
to other feedback on the kit.

jeff

  parent reply	other threads:[~2019-11-17 16:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 10:23 [C++ coroutines 0/6] Implement C++ coroutines Iain Sandoe
2019-11-17 10:24 ` [C++ coroutines 1/6] Common code and base definitions Iain Sandoe
2019-11-17 10:24   ` [C++ coroutines 2/6] Define builtins and internal functions Iain Sandoe
2019-11-17 10:26     ` [C++ coroutines 3/6] Front end parsing and transforms Iain Sandoe
2019-11-17 10:26       ` [C++ coroutines 4/6] Middle end expanders " Iain Sandoe
2019-11-17 10:27         ` [C++ coroutines 5/6] Standard library header Iain Sandoe
2019-11-17 10:28           ` [C++ coroutines 6/6] Testsuite Iain Sandoe
2019-11-19 10:01             ` Richard Biener
2020-01-09 12:40               ` [C++ coroutines 6/7, v2] Testsuite Iain Sandoe
2020-01-09 13:00                 ` Iain Sandoe
2020-01-09 13:17                 ` Richard Biener
2019-11-20 11:13             ` [C++ coroutines 6/6] Testsuite JunMa
2019-11-20 11:22               ` Iain Sandoe
2019-11-20 13:11                 ` JunMa
2019-11-17 16:19           ` [C++ coroutines 5/6] Standard library header Jonathan Wakely
2020-01-09 12:39             ` [C++ coroutines 5/7, v2] " Iain Sandoe
2020-01-09 13:50               ` Jonathan Wakely
2020-01-09 19:57                 ` [C++ coroutines 5/7, v3] " Iain Sandoe
2020-01-09 21:21                   ` Jonathan Wakely
2019-11-19 10:00         ` [C++ coroutines 4/6] Middle end expanders and transforms Richard Biener
2020-01-09 12:38           ` [C++ coroutines 4/7, v2] " Iain Sandoe
2020-01-09 14:38             ` Richard Biener
2019-11-18 13:23       ` [C++ coroutines 3/6] Front end parsing " Nathan Sidwell
2019-11-19 18:40       ` Nathan Sidwell
2020-01-09 12:37         ` [C++ coroutines 3/7, v2] " Iain Sandoe
2019-11-17 16:54     ` Jeff Law [this message]
2020-01-09 12:36       ` [C++ coroutines 2/7, v2] Define builtins and internal functions Iain Sandoe
2019-11-17 15:49   ` [C++ coroutines 1/6] Common code and base definitions Jeff Law
2020-01-09 12:36     ` [C++ coroutines 1/7] " Iain Sandoe
2019-11-18 12:35 ` [C++ coroutines 0/6] Implement C++ coroutines 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=1c45bdc4-d3b0-430a-3bf0-f8571c2c88aa@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=libstdc++@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).