From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: [libstdc++] Adjust to the new location of the C++ ABI
Date: Tue, 11 Apr 2017 22:37:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.21.1704120835500.4604@anthias.pfeifer.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1703291211420.7630@anthias.pfeifer.com>
On Thu, 30 Mar 2017, Gerald Pfeifer wrote:
> (Jonathan, I'm going to take care of the libstdc++/doc links as
> well in case you wonder.)
Done thusly.
Jonathan, do you think one of the three references in
doc/xml/manual/abi.xml could be avoided? That'll make it easier
next time this document moves. :-}
(Also, if you could regenerate and upload the docs?)
Gerald
2017-04-12 Gerald Pfeifer <gerald@pfeifer.com>
* doc/xml/faq.xml: Update reference link to C++ ABI for Itanium.
* doc/xml/manual/abi.xml. Ditto (thrice).
Index: doc/xml/faq.xml
===================================================================
--- doc/xml/faq.xml (revision 246859)
+++ doc/xml/faq.xml (working copy)
@@ -1213,7 +1213,7 @@
details than for C, and most CPU designers (for good reasons elaborated
below) have not stepped up to publish C++ ABIs. Such an ABI has been
defined for the Itanium architecture (see
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://mentorembedded.github.io/cxx-abi/">C++
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://itanium-cxx-abi.github.io/cxx-abi/">C++
ABI for Itanium</link>) and that is used by G++ and other compilers
as the de facto standard ABI on many common architectures (including x86).
G++ can also use the ARM architecture's EABI, for embedded
Index: doc/xml/manual/abi.xml
===================================================================
--- doc/xml/manual/abi.xml (revision 246859)
+++ doc/xml/manual/abi.xml (working copy)
@@ -42,7 +42,7 @@
virtual functions, etc. These details are defined as the compiler
Application Binary Interface, or ABI. The GNU C++ compiler uses an
industry-standard C++ ABI starting with version 3. Details can be
- found in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://mentorembedded.github.io/cxx-abi/abi.html">ABI
+ found in the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://itanium-cxx-abi.github.io/cxx-abi/">ABI
specification</link>.
</para>
@@ -757,7 +757,7 @@
the way the compiler deals with this class in by-value return
statements or parameters: instead of passing instances of this
class in registers, the compiler will be forced to use memory. See the
-section on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://mentorembedded.github.io/cxx-abi/abi.html#calls">Function
+section on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://itanium-cxx-abi.github.io/cxx-abi/abi.html#calls">Function
Calling Conventions and APIs</link>
of the C++ ABI documentation for further details.
</para></listitem>
@@ -1115,7 +1115,7 @@
<biblioentry xml:id="biblio.cxxabi">
<title>
<link xmlns:xlink="http://www.w3.org/1999/xlink"
- xlink:href="http://mentorembedded.github.io/cxx-abi/">
+ xlink:href="https://itanium-cxx-abi.github.io/cxx-abi/">
C++ ABI Summary
</link>
</title>
next prev parent reply other threads:[~2017-04-11 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 20:38 [wwwdocs] " Gerald Pfeifer
2017-04-11 22:31 ` Gerald Pfeifer
2017-04-11 22:37 ` Gerald Pfeifer [this message]
2017-04-19 18:11 ` [libstdc++] " Jonathan Wakely
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=alpine.LNX.2.21.1704120835500.4604@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).