From: Marek Polacek <polacek@redhat.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>, Jason Merrill <jason@redhat.com>
Subject: [wwwdocs] Introducing C++ DR status table
Date: Mon, 08 Jul 2019 17:43:00 -0000 [thread overview]
Message-ID: <20190708174302.GW5989@redhat.com> (raw)
For a long time I wished we had a table documenting the status of C++ defect
reports in the C++ FE, like clang has [1]. I finally got around to tackling
this bad boy and created <https://gcc.gnu.org/projects/cxx-dr-status.html>
and will now commit the attached patch.
The table was created by an awk script which processed
<http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_toc.html> and then I made
a lot of manual changes. I also searched through 3000 C++ PRs and linked
various PRs and changed the status of a few DRs. For this table to be
useful it needs to be much more complete, but this is a good start.
I'm not going to force anyone's hand to go over that list and update random DRs
(though *any* help would be greatly appreciated; even a list of DR #s that you
know are fixed would be useful), but please, when you fix a DR, reflect that
in the table (or let me know and I'll update it for ya). I want to see more
green!
[1] https://clang.llvm.org/cxx_dr_status.html
Index: cxx-status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cxx-status.html,v
retrieving revision 1.86
diff -u -r1.86 cxx-status.html
--- cxx-status.html 29 May 2019 08:14:45 -0000 1.86
+++ cxx-status.html 8 Jul 2019 16:41:47 -0000
@@ -21,6 +21,10 @@
<li><a href="#tses">Technical Specifications</a></li>
</ul>
+ <p>For information about the status of C++ defect reports, please see
+ <a href="https://gcc.gnu.org/projects/cxx-dr-status.html">this page</a>.
+ </p>
+
<p>For information about the status of the library implementation, please see
<a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html">this page</a>.
</p>
--
Marek Polacek ⢠Red Hat, Inc. ⢠300 A St, Boston, MA
next reply other threads:[~2019-07-08 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 17:43 Marek Polacek [this message]
2019-07-10 18:28 ` Nathan Sidwell
2019-07-10 18:29 ` Marek Polacek
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=20190708174302.GW5989@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.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).