public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 3cda2493a87ce15b079f8013d2cf096cd4d9c585
Date: Mon, 18 May 2020 20:36:36 +0000 (GMT)	[thread overview]
Message-ID: <20200518203636.0E3DD3851C05@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  3cda2493a87ce15b079f8013d2cf096cd4d9c585 (commit)
      from  3bd58e7a434375bad17806c96ff33c78c6ad5252 (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 3cda2493a87ce15b079f8013d2cf096cd4d9c585
Author: Marek Polacek <polacek@redhat.com>
Date:   Mon May 18 16:34:37 2020 -0400

    C++ DRs, gcc-11/changes: CWGs 583/1512 are implemented

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 92920476..65c02334 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -46,7 +46,14 @@ a work-in-progress.</p>
 
 <!-- <h3 id="c-family">C family</h3> -->
 
-<!-- <h3 id="cxx">C++</h3> -->
+<h3 id="cxx">C++</h3>
+<ul>
+  <li>Several C++ Defect Reports have been resolved, e.g.:
+  <ul>
+    <li>DR 1512, Pointer comparison vs qualification conversions</li>
+  </ul>
+</ul>
+
 <!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> -->
 
 <!-- <h3 id="fortran">Fortran</h3> -->
diff --git a/htdocs/projects/cxx-dr-status.html b/htdocs/projects/cxx-dr-status.html
index 54445c65..6f329710 100644
--- a/htdocs/projects/cxx-dr-status.html
+++ b/htdocs/projects/cxx-dr-status.html
@@ -4108,7 +4108,7 @@
       <td><a href="https://wg21.link/cwg583">583</a></td>
       <td>CD3</td>
       <td>Relational pointer comparisons against the null pointer constant</td>
-      <td class="unsupported">?</td>
+      <td class="supported">11</td>
       <td></td>
     </tr>
     <tr>
@@ -10615,7 +10615,7 @@
       <td><a href="https://wg21.link/cwg1512">1512</a></td>
       <td>CD3</td>
       <td>Pointer comparison vs qualification conversions</td>
-      <td class="unsupported">No</td>
+      <td class="supported">11</td>
       <td><a href="https://gcc.gnu.org/PR87699">PR87699</a></td>
     </tr>
     <tr class="open">
@@ -16972,7 +16972,7 @@
 
   <p>This page is currently maintained by <a href="mailto:polacek@redhat.com">polacek@redhat.com</a>.</p>
   <p>Last update:
-Thu 14 May 2020 07:25:07 PM EDT
+Mon 18 May 2020 04:33:44 PM EDT
   </p>
 
 </body>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-05-18 20:36 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=20200518203636.0E3DD3851C05@sourceware.org \
    --to=mpolacek@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).