public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. acd1630cbb202a79e57ee88127ad6f8c2cc2efce
Date: Mon, 27 Apr 2020 15:27:17 +0000 (GMT)	[thread overview]
Message-ID: <20200427152717.9ED293897817@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  acd1630cbb202a79e57ee88127ad6f8c2cc2efce (commit)
      from  5341e6929f04e9148ba6a1fc8d6a491593fe97f0 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit acd1630cbb202a79e57ee88127ad6f8c2cc2efce
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Mon Apr 27 08:52:56 2020 +0100

    wwwdocs: Update coroutines status.
    
    This makes minor adjustments to the coroutines status reflecting
    the changes in n4861, the C++20 standard DIS.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 3c1046bf..41c2dc0d 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -318,6 +318,7 @@ a work-in-progress.</p>
     <li>P0960R3, Parenthesized initialization of aggregates</li>
     <li>P1331R2, Allow trivial default initialization in constexpr contexts</li>
     <li>P1327R1, Allowing dynamic_cast and polymorphic typeid in constexpr contexts</li>
+    <li>P0912R5, Coroutines (requires <code>-fcoroutines</code>)</li>
   </ul>  
   </li>
   <li>Several C++ Defect Reports have been resolved, e.g.:
diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index dd2683dc..6a715058 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -444,10 +444,11 @@
     </tr>
     <tr>
       <td> Coroutines </td>
-      <td><a href="https://wg21.link/p0912r5">P0912R5</a></td>
-      <td class="supported"> <a href="../gcc-10/changes.html#cxx">10</a>
-       (<a href="../wiki/cxx-coroutines">Coroutines Wiki</a>) </td>
-      <td> </td>
+      <td><a href="https://wg21.link/p0912r5">P0912R5</a></br>
+      as applied to <a href="http://wg21.link/n4861">n4861</a></td>
+      <td class="supported"> <a href="../gcc-10/changes.html#cxx">10 </a>
+       (requires -fcoroutines)</td>
+      <td> __cpp_impl_coroutine &gt;= 201902</td>
     </tr>
     <tr>
       <td rowspan=2> Parenthesized initialization of aggregates </td>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/changes.html      | 1 +
 htdocs/projects/cxx-status.html | 9 +++++----
 2 files changed, 6 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-04-27 15:27 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=20200427152717.9ED293897817@sourceware.org \
    --to=iains@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).