From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libstdc++-return-14785-listarch-libstdc++=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 36125 invoked by alias); 20 Jan 2020 08:24:15 -0000
Mailing-List: contact libstdc++-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <libstdc++.gcc.gnu.org>
List-Subscribe: <mailto:libstdc++-subscribe@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/libstdc++/>
List-Post: <mailto:libstdc++@gcc.gnu.org>
List-Help: <mailto:libstdc++-help@gcc.gnu.org>, <http://gcc.gnu.org/ml/#faqs>
Sender: libstdc++-owner@gcc.gnu.org
Received: (qmail 35576 invoked by uid 89); 20 Jan 2020 08:24:15 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*f:sk:831D674, HX-Languages-Length:1058, H*f:sk:BD3A633
X-HELO: mail-lf1-f65.google.com
Received: from mail-lf1-f65.google.com (HELO mail-lf1-f65.google.com) (209.85.167.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 20 Jan 2020 08:24:02 +0000
Received: by mail-lf1-f65.google.com with SMTP id f24so2223265lfh.3;        Mon, 20 Jan 2020 00:24:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:references:in-reply-to:from:date:message-id:subject:to         :cc:content-transfer-encoding;        bh=noQcbpUWhbQWW1LnQ/zkaqCiIef/yHWCvAxVD4qJ160=;        b=FAuvn2xFuGprnGnzvitVb9Yy+1SuLzaBWartK6CSPki/TtksKZZz0+5JuDK5t05+BV         2rPNgb+ZOIsY5DXbMe9KZwEK7BLwwGNgBsEwRH57vf1TSwWye9PPywOhznbtSU/RC/bX         HeFlO2CriEl0145152sRhf43VI9gt6ATSE459XZVpm1Lpt2LM7m5IG81KaJHUyrCjh8F         qPNTcrAykRjM8YghRnex6u9mkId7N0UO4jTS3n3fxEfMRJG2TrZM62B3Iu0Dfk+cKWDL         72OWkZLIoUZx1PASHvqh0LexKxMVYrx/9/WeoS+m0xWo7MB3MJacal/v/oZQfxMyyj6u         G88g==
MIME-Version: 1.0
References: <BD3A6338-FFD7-4DF6-9218-F58BB3C52F0D@sandoe.co.uk> <20200118125826.GX10088@tucnak> <831D6747-A1AB-40A2-89C6-F84F80E31E19@sandoe.co.uk>
In-Reply-To: <831D6747-A1AB-40A2-89C6-F84F80E31E19@sandoe.co.uk>
From: Richard Biener <richard.guenther@gmail.com>
Date: Mon, 20 Jan 2020 08:31:00 -0000
Message-ID: <CAFiYyc37KXDR9peVVNLNuKjtwtiud6v8uXMXm81_istrtd7GQw@mail.gmail.com>
Subject: Re: [C++ coroutines] Initial implementation pushed to master.
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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2020-01/txt/msg00108.txt.bz2

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=3Dc++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=E2=80=99t want to de=
lay 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=3Dc++2a?  (I'm curious about the -fcoroutines requirement, is that bec=
ause
the implementation might still become incompatible with the actual c++2a?)

Richard.

> Iain
>