public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Patrick Palka <ppalka@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 1c4c7605f2b525140f58e3c290a40c5b9ef9ae4b
Date: Fri,  8 Apr 2022 14:11:06 +0000 (GMT)	[thread overview]
Message-ID: <20220408141106.19C213858D28@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  1c4c7605f2b525140f58e3c290a40c5b9ef9ae4b (commit)
      from  c637096c2a3d4cf33ffd610255ecd451450895fd (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 1c4c7605f2b525140f58e3c290a40c5b9ef9ae4b
Author: Patrick Palka <ppalka@redhat.com>
Date:   Fri Apr 8 10:09:43 2022 -0400

    gcc-12: Mention PR c++/51577 operator lookup fix

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index d32ac0b7..51d01418 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -290,8 +290,8 @@ a work-in-progress.</p>
   <li>New command-line option <code>-fimplicit-constexpr</code> can be used to
       make inline functions implicitly constexpr
       (<a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=87c2080b">git</a>)</li>
-  <li>New command-line option <code>-ffold-simple-inlines</code> that controls
-      whether to fold calls to certain trivial inline functions (currently
+  <li>New command-line option <code>-ffold-simple-inlines</code> can be used
+      to fold calls to certain trivial inline functions (currently
       <code>std::move</code>, <code>std::forward</code>,
       <code>std::addressof</code> and <code>std::as_const</code>).  In contrast
       to inlining such calls, folding means that no intermediate code or debug
@@ -363,6 +363,8 @@ a work-in-progress.</p>
        <a href="https://gcc.gnu.org/PR86439">PR86439</a>,
        <a href="https://gcc.gnu.org/PR98832">PR98832</a>,
       <a href="https://gcc.gnu.org/PR102933">PR102933</a> ...)</li>
+  <li>Two-stage name lookup for dependent operator expressions has been
+      corrected (<a href="https://gcc.gnu.org/PR51577">PR51577</a>)</li>
   <li>Several issues with constrained variable templates have been fixed
       (<a href="https://gcc.gnu.org/PR98486">PR98486</a>)</li>
   <li>The compiler performs less instantiating when doing speculative constant

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

Summary of changes:
 htdocs/gcc-12/changes.html | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-04-08 14:11 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=20220408141106.19C213858D28@sourceware.org \
    --to=ppalka@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).