public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marek Polacek <polacek@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3] c: Implement C23 nullptr (N3042)
Date: Thu, 25 Aug 2022 18:14:30 -0400	[thread overview]
Message-ID: <Ywf0RuuwO/ILCnPo@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2208252111490.108545@digraph.polyomino.org.uk>

On Thu, Aug 25, 2022 at 09:12:07PM +0000, Joseph Myers wrote:
> On Thu, 25 Aug 2022, Marek Polacek via Gcc-patches wrote:
> 
> > Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
> 
> This version is OK.

Thanks a lot.  I've gone ahead and updated GCC 13 changes.html:

commit 54b8bcfe7c65290942c5fccd89edd658b97774af
Author: Marek Polacek <polacek@redhat.com>
Date:   Thu Aug 25 18:12:15 2022 -0400

    gcc-13/changes: Update with recent C23 and C++23 proposals

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 03a77276..c58ca1d4 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -73,6 +73,13 @@ a work-in-progress.</p>
 
 <h3 id="c">C</h3>
 <ul>
+  <li>Several C23 features have been implemented:
+    <ul>
+      <li><a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3042.htm">N3042</a>,
+	  Introduce the nullptr constant</li>
+      <li>Support for empty initializer braces</li>
+    </ul>
+  </li>
   <li>New warnings:
     <ul>
       <li><code>-Wenum-int-mismatch</code> warns about mismatches between an
@@ -93,8 +100,20 @@ a work-in-progress.</p>
 	  reference binding to temporary
 	  (<a href="https://gcc.gnu.org/PR104477">PR104477</a>)
       </li>
+      <li><a href="https://wg21.link/p2327">P2327R1</a>, De-deprecating volatile
+	  compound operations
+      </li>
+      <li><a href="https://wg21.link/p2437">P2437R1</a>, Support for
+	  <code>#warning</code>
+	  (<a href="https://gcc.gnu.org/PR106646">PR106646</a>)
+      </li>
+      <li><a href="https://wg21.link/p2290">P2290R3</a>, Delimited escape sequences
+	  (<a href="https://gcc.gnu.org/PR106645">PR106645</a>)
+      </li>
     </ul>
   </li>
+  <li>The <code>-Wpessimizing-move</code> and <code>-Wredundant-move</code>
+      warnings have been extended to warn in more contexts.</li>
 </ul>
 
 <!-- <h4 id="libstdcxx">Runtime Library (libstdc++)</h4> -->


  reply	other threads:[~2022-08-25 22:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 21:35 [PATCH] " Marek Polacek
2022-08-15 17:48 ` Joseph Myers
2022-08-24 18:24   ` [PATCH v2] " Marek Polacek
2022-08-25 17:28     ` Joseph Myers
2022-08-25 20:51       ` [PATCH v3] " Marek Polacek
2022-08-25 21:12         ` Joseph Myers
2022-08-25 22:14           ` Marek Polacek [this message]
2022-08-15 20:03 ` [PATCH] " Jason Merrill
2022-08-24 18:24   ` 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=Ywf0RuuwO/ILCnPo@redhat.com \
    --to=polacek@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    /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).