From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] The C++ ABI specification has moved again
Date: Sun, 28 Jun 2015 00:15:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1506272124550.2176@tuna.site> (raw)
...so adjust all the links. Applied.
Gerald
Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.220
diff -u -r1.220 faq.html
--- faq.html 29 Jun 2014 20:12:59 -0000 1.220
+++ faq.html 27 Jun 2015 19:25:29 -0000
@@ -429,7 +429,7 @@
<p>For more details about the way that GCC implements these and other
C++ features, please read the <a
-href="http://mentorembedded.github.com/cxx-abi/">C++ ABI specification</a>.
+href="http://mentorembedded.github.io/cxx-abi/">C++ ABI specification</a>.
Note the <code>std::type_info</code> objects which <i>must</i> be
resolved all begin with "_ZTS". Refer to <code>ld</code>'s
documentation for a description of the "<code>-E</code>" &
Index: readings.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.238
diff -u -r1.238 readings.html
--- readings.html 27 Jun 2015 18:46:13 -0000 1.238
+++ readings.html 27 Jun 2015 19:25:29 -0000
@@ -37,7 +37,7 @@
by Joachim Nadler and Tim Josling
<<a href="mailto:tej@melbpc.org.au">tej@melbpc.org.au</a>>.</li>
- <li><a href="http://mentorembedded.github.com/cxx-abi/">
+ <li><a href="http://mentorembedded.github.io/cxx-abi/">
The V3 multi-vendor standard C++ ABI</a> is used in GCC releases 3.0 and
above.</li>
Index: gcc-4.0/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.66
diff -u -r1.66 changes.html
--- gcc-4.0/changes.html 28 Jun 2014 22:44:28 -0000 1.66
+++ gcc-4.0/changes.html 27 Jun 2015 19:25:30 -0000
@@ -182,7 +182,7 @@
<a href="#visibility"><code>-fvisibility</code> option</a>.</li>
<li>The compiler now uses the library interface specified by the <a
- href="http://mentorembedded.github.com/cxx-abi/">C++ ABI</a> for
+ href="http://mentorembedded.github.io/cxx-abi/">C++ ABI</a> for
thread-safe initialization of function-scope static variables.
Most users should leave this alone, but embedded programmers may
want to disable this by specifying
next reply other threads:[~2015-06-27 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 0:15 Gerald Pfeifer [this message]
2015-06-28 14:54 ` Gerald Pfeifer
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.LSU.2.20.1506272124550.2176@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@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).