[wwwdocs] Adjust to the new location of the C++ ABI

[wwwdocs] Adjust to the new location of the C++ ABI

[Gerald Pfeifer]

For gcc-4.0/ and faq.html I did adjust the link, for gcc-3.2/ I
figured we can as well avoid it.

Applied.

(Jonathan, I'm going to take care of the libstdc++/doc links as
well in case you wonder.)

Gerald

Index: faq.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.224
diff -u -r1.224 faq.html
--- faq.html	3 Feb 2017 07:43:57 -0000	1.224
+++ faq.html	29 Mar 2017 09:10:23 -0000
@@ -428,7 +428,7 @@
 
 <p>For more details about the way that GCC implements these and other
 C++ features, please read the <a
-href="http://mentorembedded.github.io/cxx-abi/">C++ ABI specification</a>.
+href="https://itanium-cxx-abi.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>" &amp;

Index: gcc-3.2/c++-abi.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/c++-abi.html,v
retrieving revision 1.9
retrieving revision 1.11
diff -u -r1.9 -r1.11
--- gcc-3.2/c++-abi.html	1 Feb 2017 20:18:54 -0000	1.9
+++ gcc-3.2/c++-abi.html	30 Mar 2017 20:36:53 -0000	1.11
@@ -9,10 +9,9 @@
     <p>
     The main point of the GCC 3.2 release is to have a relatively
     stable and common C++ ABI for GNU/Linux and BSD usage, following
-    the documentation at
-    <a href="http://mentorembedded.github.io/cxx-abi/">http://mentorembedded.github.io/cxx-abi/</a>.
+    the Itanium C++ ABI.</p>
    
-    Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0
+    <p>Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0
     and GCC 3.1 releases.</p>
 
     <p>

Index: gcc-4.0/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.69
diff -u -r1.69 changes.html
--- gcc-4.0/changes.html	19 Mar 2017 19:07:26 -0000	1.69
+++ gcc-4.0/changes.html	29 Mar 2017 09:10:24 -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.io/cxx-abi/">C++ ABI</a> for
+        href="https://itanium-cxx-abi.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

Re: [wwwdocs] Adjust to the new location of the C++ ABI

[Gerald Pfeifer]

On Thu, 30 Mar 2017, Gerald Pfeifer wrote:
> For gcc-4.0/ and faq.html I did adjust the link, for gcc-3.2/ I
> figured we can as well avoid it.

And here was another one...

Applied.

Gerald

Index: readings.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.275
diff -u -r1.275 readings.html
--- readings.html	1 Apr 2017 20:02:50 -0000	1.275
+++ readings.html	11 Apr 2017 22:29:59 -0000
@@ -37,7 +37,7 @@
   by Joachim Nadler and Tim Josling
   &lt;<a href="mailto:tej@melbpc.org.au">tej@melbpc.org.au</a>&gt;.</li>
 
-  <li><a href="http://mentorembedded.github.io/cxx-abi/">
+  <li><a href="https://itanium-cxx-abi.github.io/cxx-abi/">
   The V3 multi-vendor standard C++ ABI</a> is used in GCC releases 3.0 and
   above.</li>
 

[libstdc++] Adjust to the new location of the C++ ABI

[Gerald Pfeifer]

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>

Re: [libstdc++] Adjust to the new location of the C++ ABI

[Jonathan Wakely]

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

On 12/04/17 08:37 +1000, Gerald Pfeifer wrote:
>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. :-}

Well, they go to three different places (or did, before your change).

One link was the the ABI spec, one is to a specific section of the
spec, and one is a bibliography entry linking to the homepage of the
project. I've changed the first one to link to the bibliography entry,
so there are only two now, but I don't think it's am improvement
really. When you click on the link it jumps to the bottom of the
page, but not necessarily to the actual anchor (because it's too near
the bottom of the page).

I certainly don't think we should remove the second one. I
don't want to have a hypertext document that says "see section N of
[biblio.cxxabi]" rather than just hyperlinking directly to it.

>(Also, if you could regenerate and upload the docs?)

Sure.

Committed to trunk.



[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 2703 bytes --]

commit ed7eeb361974a8c64803b617bd760612060cc3ab
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Apr 19 17:45:42 2017 +0100

    Rationalise ABI links in libstdc++ manual
    
    	* doc/xml/manual/abi.xml: Rephrase one of the references to the
    	Itanium C++ ABI.
    	* doc/xml/manual/test.xml: Document DejaGnu 1.5.3 requirement.
    	* doc/html/*: Regenerate.

diff --git a/libstdc++-v3/doc/xml/manual/abi.xml b/libstdc++-v3/doc/xml/manual/abi.xml
index 0e56068..1c816b1 100644
--- a/libstdc++-v3/doc/xml/manual/abi.xml
+++ b/libstdc++-v3/doc/xml/manual/abi.xml
@@ -40,10 +40,9 @@
   alignment and in a particular layout, mangling names according to a
   well-defined algorithm, has specific arrangements for the support of
   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="https://itanium-cxx-abi.github.io/cxx-abi/">ABI
-  specification</link>.
+  Application Binary Interface, or ABI. From GCC version 3 onwards the
+  GNU C++ compiler uses an industry-standard C++ ABI, the
+  <link linkend="biblio.cxxabi">Itanium C++ ABI</link>.
 </para>
 
 <para>
@@ -1116,7 +1115,7 @@ gcc test.c -g -O2 -L. -lone -ltwo /usr/lib/libstdc++.so.5 /usr/lib/libstdc++.so.
       <title>
 	<link xmlns:xlink="http://www.w3.org/1999/xlink"
 	      xlink:href="https://itanium-cxx-abi.github.io/cxx-abi/">
-	  C++ ABI Summary
+	  Itanium C++ ABI
 	</link>
       </title>
     </biblioentry>
diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml
index 8ae88b3..7cb7daf 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -563,8 +563,11 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
       the <varname>CXXFLAGS</varname> variable when running
       <command>make</command>, or via options for the DejaGnu test framework
       (described below). The latter approach uses the
-      <option>--target_board</option> option that was shown earlier.
-      For example, to run the tests with <option>-O1 -D_GLIBCXX_ASSERTIONS</option>
+      <option>--target_board</option> option that was shown earlier,
+      but requires DejaGnu version 1.5.3 or newer to work reliably, so that the
+      <literal>dg-options</literal> in the test aren't overridden.
+      For example, to run the tests with
+      <option>-O1 -D_GLIBCXX_ASSERTIONS</option>
       you could use:
 <programlisting>    make RUNTESTFLAGS=--target_board=unix/-O1/-D_GLIBCXX_ASSERTIONS</programlisting>
     </para>