From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Document zero width bit-field passing ABI changes in gcc-12/changes.html [PR104796]
Date: Sat, 22 Oct 2022 18:47:27 +0200 (CEST) [thread overview]
Message-ID: <1f93c86b-3454-667a-4d0c-3ccc4e663154@pfeifer.com> (raw)
In-Reply-To: <YkQ/Wa8IStHvIvLE@tucnak>
On Wed, 30 Mar 2022, Jakub Jelinek via Gcc-patches wrote:
> Thanks, changed and committed.
This (commit 3be1a28f58d6063258407b0751e8fb55df4749c8) introduced a new
<a name=...> which is deprecated HTML.
Below is the straightforward adjustment I just pushed.
Gerald
commit 95e5070662283453db934dee37203ce9db6e342c
Author: Gerald Pfeifer <gerald@pfeifer.com>
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
<!-- .................................................................. -->
<h2>Caveats</h2>
<ul>
- <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="https://gcc.gnu.org/PR102024">PR102024</a>,
next prev parent reply other threads:[~2022-10-22 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:07 Jakub Jelinek
2022-03-30 11:00 ` Richard Biener
2022-03-30 11:30 ` Jakub Jelinek
2022-10-22 16:47 ` Gerald Pfeifer [this message]
2022-03-30 12:10 ` Richard Earnshaw
2022-03-30 12:13 ` Richard Earnshaw
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=1f93c86b-3454-667a-4d0c-3ccc4e663154@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
/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).