From: Richard Biener <richard.guenther@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [C++ coroutines] Initial implementation pushed to master.
Date: Mon, 20 Jan 2020 08:31:00 -0000 [thread overview]
Message-ID: <CAFiYyc37KXDR9peVVNLNuKjtwtiud6v8uXMXm81_istrtd7GQw@mail.gmail.com> (raw)
In-Reply-To: <831D6747-A1AB-40A2-89C6-F84F80E31E19@sandoe.co.uk>
On Sat, Jan 18, 2020 at 2:02 PM Iain Sandoe <iain@sandoe.co.uk> wrote:
>
> Hi Jakub,
>
> Jakub Jelinek <jakub@redhat.com> wrote:
>
> > On Sat, Jan 18, 2020 at 12:53:48PM +0000, Iain Sandoe wrote:
> > Thanks.
> >
> > Shouldn't this be mentioned in https://gcc.gnu.org/projects/cxx-status.html
> > ?
> >
> >> * This is not enabled by default (even for -std=c++2a), it needs
> >> -fcoroutines.
> >
> > And, if this is the planned case even for GCC 10 release, I think the
> > -fcoroutines option needs to be mentioned there too.
>
> Yes, (and I also need to update the wiki), just didn’t want to delay the
> commit any
> more.
>
> I will get onto those (on Monday probably).
It also deserves a changes.html entry in the C++ parts. Does the compiler
hint at using -fcoroutines when the user tries to use those and specifies
-std=c++2a? (I'm curious about the -fcoroutines requirement, is that because
the implementation might still become incompatible with the actual c++2a?)
Richard.
> Iain
>
next prev parent reply other threads:[~2020-01-20 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 12:58 Iain Sandoe
2020-01-18 13:02 ` Jakub Jelinek
2020-01-20 3:06 ` Iain Sandoe
2020-01-20 8:31 ` Richard Biener [this message]
2020-01-20 21:53 ` Iain Sandoe
2024-03-05 17:31 ` H.J. Lu
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=CAFiYyc37KXDR9peVVNLNuKjtwtiud6v8uXMXm81_istrtd7GQw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=jakub@redhat.com \
--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).