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. 2f6aed80eb795f66a26cab2b5eee598d68f76ae5
Date: Tue, 15 Sep 2020 01:14:50 +0000 (GMT)	[thread overview]
Message-ID: <20200915011450.8D8B63857C42@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  2f6aed80eb795f66a26cab2b5eee598d68f76ae5 (commit)
      from  2feaab534eb731bfc91f41b9e6f4afe9f6898828 (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 2f6aed80eb795f66a26cab2b5eee598d68f76ae5
Author: Marek Polacek <polacek@redhat.com>
Date:   Mon Sep 14 21:14:39 2020 -0400

    Fix <p> tags.

diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html
index e51285d9..5db00734 100644
--- a/htdocs/gcc-11/porting_to.html
+++ b/htdocs/gcc-11/porting_to.html
@@ -46,13 +46,12 @@ use the <code>-std=gnu++14</code> command-line option, perhaps by putting it
 in <code>CXXFLAGS</code> or similar variables in Makefiles.</p>
 
 <h3 id="template-template-changes">Template template parameter matching changes</h3>
-<p>
-G++, starting with
+<p>G++, starting with
 <a href="https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=31bfc9b9">G++ 7</a>,
 implements C++17
 <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0522r0.html">P0522R0</a>,
 Matching of template template-arguments excludes compatible templates.  As a
-consequence, the following test is now rejected:
+consequence, the following test is now rejected:</p>
 <pre><code>
     template &lt;int N, int M = N&gt; class A;
     template &lt;int N, int M&gt; void fn(A&lt;N, M&gt; &amp;) {}
@@ -60,15 +59,12 @@ consequence, the following test is now rejected:
     template void fn(A&lt;3&gt; &amp;);
 </code></pre>
 
-because <code>A</code> is now considered a valid argument for <code>TT</code>,
+<p>because <code>A</code> is now considered a valid argument for <code>TT</code>,
 so both function templates are valid candidates, and neither is more specialized
-than the other, so it's ambiguous.
-</p>
-<p>
-The new behavior can be disabled independently of other C++17 features with
-<code>-fno-new-ttp-matching</code>.
-</p>
+than the other, so it's ambiguous.</p>
 
+<p>The new behavior can be disabled independently of other C++17 features with
+<code>-fno-new-ttp-matching</code>.</p>
 
 <!--
 <h2 id="fortran">Fortran language issues</h2>

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

Summary of changes:
 htdocs/gcc-11/porting_to.html | 16 ++++++----------
 1 file changed, 6 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-09-15  1:14 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=20200915011450.8D8B63857C42@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).