public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: msebor@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. a3bcd42bc345f3f1f45f93a3c95b954c9868586f
Date: Thu, 23 Jan 2020 10:00:00 -0000	[thread overview]
Message-ID: <20200123100052.43783.qmail@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  a3bcd42bc345f3f1f45f93a3c95b954c9868586f (commit)
      from  26243d7b0213edbfba25c5fb2ae09103e55609d5 (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 a3bcd42bc345f3f1f45f93a3c95b954c9868586f
Author: Martin Sebor <msebor@redhat.com>
Date:   Thu Jan 23 11:00:06 2020 +0100

    Correct errors pointed out by validator.w3.org.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index fb1b108..6e75215 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -119,12 +119,14 @@ a work-in-progress.</p>
 <ul>
   <li>New attributes:
     <ul>
-      The <code>access</code> function and type attribute has been added
-      to describe how a function accesses objects passed to it by pointer
-      or reference, and to associate such arguments with integer arguments
-      denoting the objects' sizes.  The attribute is used to enable
-      the detection of invalid accesses by user-defined functions, such
-      as those diagnosed by <code>-Wstringop-overflow</code>.
+     <li>
+       The <code>access</code> function and type attribute has been added
+       to describe how a function accesses objects passed to it by pointer
+       or reference, and to associate such arguments with integer arguments
+       denoting the objects' sizes.  The attribute is used to enable
+       the detection of invalid accesses by user-defined functions, such
+       as those diagnosed by <code>-Wstringop-overflow</code>.
+     </li>
     </ul>
   </li>
   <li>New warnings:
@@ -254,18 +256,19 @@ a work-in-progress.</p>
   </li>
   <li>New warnings:
     <ul>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/C_002b_002b-Dialect-Options.html#C_002b_002b-Dialect-Options#index-Wmismatched-tags"><code>-Wmismatched-tags</code></a>,
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wmismatched-tags"><code>-Wmismatched-tags</code></a>,
 	disabled by default, warns about declarations of structs, classes,
 	and class templates and their specializations with a class-key that
 	does not match either the definition or the first declaration if no
 	definition is provided.  The option is provided to ease portability
 	to Windows-based compilers.
       </li>
-      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/C_002b_002b-Dialect-Options.html#C_002b_002b-Dialect-Options#index-Wredundant-tags"><code>-Wredundant-tags</code></a>,
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Wredundant-tags"><code>-Wredundant-tags</code></a>,
 	disabled by default, warns about redundant <i>class-key</i> and
 	<i>enum-key</i> in contexts where the key can be eliminated without
 	causing an syntactic ambiguity.
       </li>
+    </ul>
   <li>
     G++ can now detect modifying constant objects in constexpr evaluation
     (which is undefined behavior).

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-23 10:00 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=20200123100052.43783.qmail@sourceware.org \
    --to=msebor@gcc.gnu.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).