summaryrefslogtreecommitdiff
path: root/libstdc++-v3/doc/xml/manual/internals.xml
diff options
context:
space:
mode:
Diffstat (limited to 'libstdc++-v3/doc/xml/manual/internals.xml')
-rw-r--r--libstdc++-v3/doc/xml/manual/internals.xml47
1 files changed, 24 insertions, 23 deletions
diff --git a/libstdc++-v3/doc/xml/manual/internals.xml b/libstdc++-v3/doc/xml/manual/internals.xml
index 63664cea3f1..72af0b835c8 100644
--- a/libstdc++-v3/doc/xml/manual/internals.xml
+++ b/libstdc++-v3/doc/xml/manual/internals.xml
@@ -1,7 +1,8 @@
-<sect1 id="appendix.porting.internals" xreflabel="Portin Internals">
+<section xmlns="http://docbook.org/ns/docbook" version="5.0"
+ xml:id="appendix.porting.internals" xreflabel="Portin Internals">
<?dbhtml filename="internals.html"?>
-<sect1info>
+<info><title>Porting to New Hardware or Operating Systems</title>
<keywordset>
<keyword>
ISO C++
@@ -10,9 +11,9 @@
internals
</keyword>
</keywordset>
-</sect1info>
+</info>
+
-<title>Porting to New Hardware or Operating Systems</title>
<para>
</para>
@@ -45,8 +46,8 @@ a "host." The comment at the top of <code>configure.ac</code> explains why.)
</para>
-<sect2 id="internals.os">
-<title>Operating System</title>
+<section xml:id="internals.os"><info><title>Operating System</title></info>
+
<para>If you are porting to a new operating system (as opposed to a new chip
using an existing operating system), you will need to create a new
@@ -151,11 +152,11 @@ this:
<para>We recommend copying an existing <code>os_defines.h</code> to use as a
starting point.
</para>
-</sect2>
+</section>
-<sect2 id="internals.cpu">
-<title>CPU</title>
+<section xml:id="internals.cpu"><info><title>CPU</title></info>
+
<para>If you are porting to a new chip (as opposed to a new operating system
running on an existing chip), you will need to create a new directory in the
@@ -183,11 +184,11 @@ example, <code>alpha</code>, <code>alphaev5</code>, and <code>alphaev6</code> al
appropriate for your chip.
</para>
-</sect2>
+</section>
+
+<section xml:id="internals.char_types"><info><title>Character Types</title></info>
-<sect2 id="internals.char_types">
-<title>Character Types</title>
<para>The library requires that you provide three header files to implement
character classification, analogous to that provided by the C libraries
@@ -399,11 +400,11 @@ from <code>__low</code> up until <code>__high</code> into the vector given by
}
</programlisting>
-</sect2>
+</section>
-<sect2 id="internals.thread_safety">
-<title>Thread Safety</title>
+<section xml:id="internals.thread_safety"><info><title>Thread Safety</title></info>
+
<para>The C++ library string functionality requires a couple of atomic
operations to provide thread-safety. If you don't take any special
@@ -482,11 +483,11 @@ must be equivalent to those provided here, but using atomic operations:
}
</programlisting>
-</sect2>
+</section>
+
+<section xml:id="internals.numeric_limits"><info><title>Numeric Limits</title></info>
-<sect2 id="internals.numeric_limits">
-<title>Numeric Limits</title>
<para>The C++ library requires information about the fundamental data types,
such as the minimum and maximum representable values of each type.
@@ -504,11 +505,11 @@ To take that approach, create a new file called <code>cpu_limits.h</code> in
your CPU configuration directory (see <link linkend="internals.cpu">CPU</link>).
</para>
-</sect2>
+</section>
+
+<section xml:id="internals.libtool"><info><title>Libtool</title></info>
-<sect2 id="internals.libtool">
-<title>Libtool</title>
<para>The C++ library is compiled, archived and linked with libtool.
Explaining the full workings of libtool is beyond the scope of this
@@ -543,6 +544,6 @@ operating system.
</para>
-</sect2>
+</section>
-</sect1>
+</section>