public inbox for
help / color / mirror / Atom feed
From: Gerald Pfeifer <>
Subject: gcc-wwwdocs branch master updated. 95e5070662283453db934dee37203ce9db6e342c
Date: Sat, 22 Oct 2022 16:42:53 +0000 (GMT)	[thread overview]
Message-ID: <> (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  95e5070662283453db934dee37203ce9db6e342c (commit)
      from  f3541cfb120e4e5f0f6fed3ebe6d5a4c36a8079a (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 95e5070662283453db934dee37203ce9db6e342c
Author: Gerald Pfeifer <>
Date:   Sat Oct 22 18:41:14 2022 +0200

    gcc-12: Replace an <a name=...> by an id=
    The name attribute for the <a> tag has been obsoleted. Use an id= on
    the nearest container instead, as we already do everywhere else.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 0e56aba0..30fa4d6e 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -25,8 +25,7 @@ You may also want to check out our
 <!-- .................................................................. -->
-  <li>
-    An <a name="zero_width_bitfields">ABI</a> incompatibility between C and
+  <li id="zero_width_bitfields">An ABI incompatibility between C and
     C++ when passing or returning by value certain aggregates containing zero
     width bit-fields has been discovered on various targets.
     As mentioned in <a href="">PR102024</a>,


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


                 reply	other threads:[~2022-10-22 16: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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).