public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. e9b7ac22fa802bf1e1fd08a26c7ae2e1580ffadd
Date: Sun, 17 May 2020 13:42:10 +0000 (GMT)	[thread overview]
Message-ID: <20200517134210.2955F385BF81@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3200 bytes --]

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  e9b7ac22fa802bf1e1fd08a26c7ae2e1580ffadd (commit)
       via  bb406fa02b9a9c47861bc2246513c198bffc90bb (commit)
      from  93538bdb512831e9e9175b2c5c0bfb1527407b79 (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 e9b7ac22fa802bf1e1fd08a26c7ae2e1580ffadd
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sun May 17 15:40:59 2020 +0200

    Use <a id=...> instead of <a name=...> for the C++ ABI changes.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 2a94b13d..af40b3ad 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -411,7 +411,7 @@ int get_naïve_pi() {
     <code>namespace</code>s too.
   </li>
   <li>
-    <a name="empty_base">The ABI</a>
+    <a id="empty_base">The ABI</a>
     of passing and returning certain C++ classes by value changed
     on several targets in GCC 10, including
     <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94383">AArch64</a>,

commit bb406fa02b9a9c47861bc2246513c198bffc90bb
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat May 16 18:14:36 2020 +0200

    Further markup fixes, properly closing <code> elements.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index ce2efe00..2a94b13d 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -805,17 +805,17 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512)));
   now supports this option.</li>
   <li>Support for the
   <a href="https://developer.arm.com/architectures/cpu-architecture/m-profile">
-  Armv8.1-M Mainline</a> Architecture has been added.</li>
+  Armv8.1-M Mainline</a> Architecture has been added.
   <ul>
     <li>Armv8.1-M Mainline can be enabled by using the
-      <code>-march=armv8.1-m.main<code> command-line option.</li>
-  </ul>
+      <code>-march=armv8.1-m.main</code> command-line option.</li>
+  </ul></li>
   <li>Support for the
   <a href="https://developer.arm.com/architectures/instruction-sets/simd-isas/helium/helium-intrinsics">
   MVE</a> beta ACLE intrinsics has been added. These intrinsics can be
   enabled by including the arm_mve.h header file and passing the
-  <code>+mve<code> or <code>+mve.fp<code> option extensions (for
-  example: <code>-march=armv8.1-m.main+mve<code>).</li>
+  <code>+mve</code> or <code>+mve.fp</code> option extensions (for
+  example: <code>-march=armv8.1-m.main+mve</code>).</li>
   <li>Support for the Custom Datapath Extension beta ACLE
   <a href="https://developer.arm.com/docs/101028/0010/custom-datapath-extension">
   intrinsics</a> has been added.</li>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-05-17 13:42 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=20200517134210.2955F385BF81@sourceware.org \
    --to=gerald@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).