Very boring. Committed to trunk.
commit 16d0b033ca4d3dd1331c58730c7944ae6e648a14
Author: Jonathan Wakely <jwak...@redhat.com>
Date: Tue Oct 13 16:43:11 2020
libstdc++: Remove trailing whitespace from XML docs
libstdc++-v3/ChangeLog:
* doc/xml/book.txml: Remove trailing whitespace.
* doc/xml/chapter.txml: Likewise.
* doc/xml/class.txml: Likewise.
* doc/xml/gnu/fdl-1.3.xml: Likewise.
* doc/xml/gnu/gpl-3.0.xml: Likewise.
* doc/xml/manual/abi.xml: Likewise.
* doc/xml/manual/algorithms.xml: Likewise.
* doc/xml/manual/allocator.xml: Likewise.
* doc/xml/manual/appendix_contributing.xml: Likewise.
* doc/xml/manual/appendix_free.xml: Likewise.
* doc/xml/manual/appendix_porting.xml: Likewise.
* doc/xml/manual/atomics.xml: Likewise.
* doc/xml/manual/auto_ptr.xml: Likewise.
* doc/xml/manual/backwards_compatibility.xml: Likewise.
* doc/xml/manual/bitmap_allocator.xml: Likewise.
* doc/xml/manual/build_hacking.xml: Likewise.
* doc/xml/manual/codecvt.xml: Likewise.
* doc/xml/manual/concurrency.xml: Likewise.
* doc/xml/manual/concurrency_extensions.xml: Likewise.
* doc/xml/manual/configure.xml: Likewise.
* doc/xml/manual/containers.xml: Likewise.
* doc/xml/manual/ctype.xml: Likewise.
* doc/xml/manual/debug.xml: Likewise.
* doc/xml/manual/debug_mode.xml: Likewise.
* doc/xml/manual/diagnostics.xml: Likewise.
* doc/xml/manual/documentation_hacking.xml: Likewise.
* doc/xml/manual/evolution.xml: Likewise.
* doc/xml/manual/internals.xml: Likewise.
* doc/xml/manual/intro.xml: Likewise.
* doc/xml/manual/io.xml: Likewise.
* doc/xml/manual/iterators.xml: Likewise.
* doc/xml/manual/locale.xml: Likewise.
* doc/xml/manual/localization.xml: Likewise.
* doc/xml/manual/messages.xml: Likewise.
* doc/xml/manual/mt_allocator.xml: Likewise.
* doc/xml/manual/numerics.xml: Likewise.
* doc/xml/manual/parallel_mode.xml: Likewise.
* doc/xml/manual/policy_data_structures.xml: Likewise.
* doc/xml/manual/prerequisites.xml: Likewise.
* doc/xml/manual/shared_ptr.xml: Likewise.
* doc/xml/manual/spine.xml: Likewise.
* doc/xml/manual/status_cxxtr1.xml: Likewise.
* doc/xml/manual/status_cxxtr24733.xml: Likewise.
* doc/xml/manual/strings.xml: Likewise.
* doc/xml/manual/support.xml: Likewise.
* doc/xml/manual/test.xml: Likewise.
* doc/xml/manual/test_policy_data_structures.xml: Likewise.
* doc/xml/manual/using.xml: Likewise.
* doc/xml/manual/using_exceptions.xml: Likewise.
* doc/xml/manual/utilities.xml: Likewise.
* doc/html/*: Regenerate.
diff --git a/libstdc++-v3/doc/xml/book.txml b/libstdc++-v3/doc/xml/book.txml
index 55b050271a5..8e3f3273c34 100644
--- a/libstdc++-v3/doc/xml/book.txml
+++ b/libstdc++-v3/doc/xml/book.txml
@@ -2,7 +2,7 @@
<book xmlns="http://docbook.org/ns/docbook"; version="5.0" xml:id="api"
xreflabel="Source Level Documentation">
-
+
<info>
<copyright>
<year>2007</year>
@@ -13,7 +13,7 @@
</copyright>
<legalnotice>
<para>
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="17_intro/license.html">License
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="17_intro/license.html">License
</link>
</para>
</legalnotice>
@@ -22,7 +22,7 @@
<part><info><title/></info>
<chapter><info><title/></info>
-
+
<para/>
</chapter>
</part>
diff --git a/libstdc++-v3/doc/xml/chapter.txml
b/libstdc++-v3/doc/xml/chapter.txml
index b251c84609a..a5a9a3a8230 100644
--- a/libstdc++-v3/doc/xml/chapter.txml
+++ b/libstdc++-v3/doc/xml/chapter.txml
@@ -1,7 +1,7 @@
<!-- Converted by db4-upgrade version 1.0 -->
<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro" xreflabel="Introduction">
-
+
<info><title>Introduction</title>
<keywordset>
<keyword>ISO C++</keyword>
@@ -12,33 +12,33 @@
<section xml:id="manual.intro.status"
xreflabel="Status"><info><title>Status</title></info>
-
+
<para>
The GNU C++ ...
</para>
</section>
<section xml:id="manual.intro.setup"
xreflabel="Setup"><info><title>Setup</title></info>
-
+
<para>
The GNU C++ ...
</para>
<section xml:id="manual.intro.setup.next1"
xreflabel="Next1"><info><title>Next1</title></info>
-
+
<para>
The GNU C++ ...
</para>
</section>
<section xml:id="manual.intro.setup.next2"
xreflabel="Next2"><info><title>Next2</title></info>
-
+
<para>
The GNU C++ ...
</para>
- </section>
+ </section>
</section>
<section xml:id="manual.intro.using"
xreflabel="Using"><info><title>Using</title></info>
-
+
<para>
The GNU C++ ...
</para>
diff --git a/libstdc++-v3/doc/xml/class.txml b/libstdc++-v3/doc/xml/class.txml
index be0929b7046..8d96d2cb0fa 100644
--- a/libstdc++-v3/doc/xml/class.txml
+++ b/libstdc++-v3/doc/xml/class.txml
@@ -2,7 +2,7 @@
<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.util.memory.allocator" xreflabel="allocator">
<?dbhtml filename="allocator.html"?>
-
+
<info><title>allocator</title>
<keywordset>
<keyword>ISO C++</keyword>
@@ -31,7 +31,7 @@
</listitem>
</itemizedlist>
- <para>
+ <para>
</para>
</section>
@@ -41,7 +41,7 @@
<para>
</para>
- <para>
+ <para>
</para>
</section>
@@ -49,19 +49,19 @@
<section><info><title>Interface Design</title></info>
-
+
<para>
</para>
-
- <para>
+
+ <para>
</para>
</section>
<section><info><title>Selecting Default Allocation Strategy</title></info>
-
- <para>
+
+ <para>
</para>
<orderedlist>
@@ -77,12 +77,12 @@
</section>
<section><info><title>Disabling Memory Caching</title></info>
-
- <para>
+
+ <para>
</para>
- <para>
+ <para>
</para>
</section>
</section>
@@ -97,22 +97,22 @@
<section xml:id="allocator.custom"
xreflabel="allocator.custom"><info><title>Custom Allocators</title></info>
- <para>
+ <para>
</para>
- <para>
+ <para>
</para>
</section>
<bibliography xml:id="allocator.biblio" xreflabel="allocator.biblio">
-<info>
+<info>
<title>
Bibliography
</title>
</info>
-<!--
+<!--
<biblioentry xml:id="biblio.xxx">
<title>
<link xmlns:xlink="http://www.w3.org/1999/xlink";
@@ -121,7 +121,7 @@
</link>
</title>
<date>
-
+
</date>
<authorgroup>
diff --git a/libstdc++-v3/doc/xml/gnu/fdl-1.3.xml
b/libstdc++-v3/doc/xml/gnu/fdl-1.3.xml
index 10c8106ca16..a1f8357ed25 100644
--- a/libstdc++-v3/doc/xml/gnu/fdl-1.3.xml
+++ b/libstdc++-v3/doc/xml/gnu/fdl-1.3.xml
@@ -1,8 +1,8 @@
-<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.gfdl-1.3">
<info><title>GNU Free Documentation License</title></info>
<?dbhtml filename="appendix_gfdl.html"?>
-
+
<simpara>Version 1.3, 3 November 2008</simpara>
<simpara>
Copyright © 2000, 2001, 2002, 2007, 2008
diff --git a/libstdc++-v3/doc/xml/gnu/gpl-3.0.xml
b/libstdc++-v3/doc/xml/gnu/gpl-3.0.xml
index f3d1c07fe3f..05f940d26ca 100644
--- a/libstdc++-v3/doc/xml/gnu/gpl-3.0.xml
+++ b/libstdc++-v3/doc/xml/gnu/gpl-3.0.xml
@@ -1,9 +1,9 @@
-<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.gpl-3.0"><info><title>
<acronym>GNU</acronym> General Public License version 3
</title></info>
<?dbhtml filename="appendix_gpl.html"?>
-
+
<para>
Version 3, 29 June 2007
</para>
diff --git a/libstdc++-v3/doc/xml/manual/abi.xml
b/libstdc++-v3/doc/xml/manual/abi.xml
index 7aec810d45f..e9f3773186c 100644
--- a/libstdc++-v3/doc/xml/manual/abi.xml
+++ b/libstdc++-v3/doc/xml/manual/abi.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.porting.abi" xreflabel="abi">
<?dbhtml filename="abi.html"?>
@@ -103,7 +103,7 @@ as to give distinct versions to the C++ interface.
</para>
<section xml:id="abi.versioning.goals"><info><title>Goals</title></info>
-
+
<para>Extending existing, stable ABIs. Versioning gives subsequent
releases of library binaries the ability to add new symbols and add
@@ -126,7 +126,7 @@ compatible.
</section>
<section xml:id="abi.versioning.history"><info><title>History</title></info>
-
+
<para>
How can this complexity be managed? What does C++ versioning mean?
@@ -600,7 +600,7 @@ compatible.
</section>
<section
xml:id="abi.versioning.prereq"><info><title>Prerequisites</title></info>
-
+
<para>
Minimum environment that supports a versioned ABI: A supported
dynamic linker, a GNU linker of sufficient vintage to understand
@@ -624,7 +624,7 @@ compatible.
</section>
<section
xml:id="abi.versioning.config"><info><title>Configuring</title></info>
-
+
<para>
It turns out that most of the configure options that change
@@ -654,7 +654,7 @@ compatible.
</section>
<section xml:id="abi.versioning.active"><info><title>Checking
Active</title></info>
-
+
<para>
When the GNU C++ library is being built with symbol versioning
@@ -907,7 +907,7 @@ standard includes.</para>
<section xml:id="abi.testing.single"><info><title>Single ABI
Testing</title></info>
-
+
<para>
Testing for GNU C++ ABI changes is composed of two distinct
@@ -1005,7 +1005,7 @@ us. We'd like to know about them!
</section>
<section xml:id="abi.testing.multi"><info><title>Multiple ABI
Testing</title></info>
-
+
<para>
A "C" application, dynamically linked to two shared libraries, liba,
libb. The dependent library liba is a C++ shared library compiled with
diff --git a/libstdc++-v3/doc/xml/manual/algorithms.xml
b/libstdc++-v3/doc/xml/manual/algorithms.xml
index e776d6e3e55..eba1edc9706 100644
--- a/libstdc++-v3/doc/xml/manual/algorithms.xml
+++ b/libstdc++-v3/doc/xml/manual/algorithms.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.algorithms" xreflabel="Algorithms">
<?dbhtml filename="algorithms.html"?>
@@ -65,13 +65,13 @@
<!-- Sect1 02 : Mutating -->
<section xml:id="std.algorithms.mutating"
xreflabel="Mutating"><info><title>Mutating</title></info>
-
+
<section xml:id="algorithms.mutating.swap"
xreflabel="swap"><info><title><function>swap</function></title></info>
-
+
<section xml:id="algorithms.swap.specializations"
xreflabel="Specializations"><info><title>Specializations</title></info>
-
+
<para>If you call <code> std::swap(x,y); </code> where x and y are standard
containers, then the call will automatically be replaced by a call to
diff --git a/libstdc++-v3/doc/xml/manual/allocator.xml
b/libstdc++-v3/doc/xml/manual/allocator.xml
index d8a255ca213..1f429410eb0 100644
--- a/libstdc++-v3/doc/xml/manual/allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/allocator.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.util.memory.allocator" xreflabel="Allocator">
<?dbhtml filename="allocator.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
index 4380cbbe3f1..d346b922907 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_contributing.xml
@@ -1,4 +1,4 @@
-<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.contrib" xreflabel="Contributing">
<?dbhtml filename="appendix_contributing.html"?>
@@ -28,10 +28,10 @@
</para>
<section xml:id="contrib.list" xreflabel="Contributor
Checklist"><info><title>Contributor Checklist</title></info>
-
+
<section xml:id="list.reading"><info><title>Reading</title></info>
-
+
<itemizedlist>
<listitem>
@@ -89,7 +89,7 @@
</section>
<section xml:id="list.copyright"><info><title>Assignment</title></info>
-
+
<para>
See the <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/contribute.html#legal";>legal
prerequisites</link> for all GCC contributions.
</para>
@@ -124,7 +124,7 @@
</section>
<section xml:id="list.getting"><info><title>Getting Sources</title></info>
-
+
<para>
<link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/gitwrite.html";>Getting write access
(look for "Write after approval")</link>
@@ -132,7 +132,7 @@
</section>
<section xml:id="list.patches"><info><title>Submitting Patches</title></info>
-
+
<para>
Every patch must have several pieces of information before it can be
@@ -196,7 +196,7 @@
<section xml:id="contrib.organization" xreflabel="Source
Organization"><info><title>Directory Layout and Source
Conventions</title></info>
<?dbhtml filename="source_organization.html"?>
-
+
<para>
The <filename class="directory">libstdc++-v3</filename> directory in the
@@ -409,7 +409,7 @@ indicate a place that may require attention for
multi-thread safety.
<section xml:id="contrib.coding_style" xreflabel="Coding
Style"><info><title>Coding Style</title></info>
<?dbhtml filename="source_code_style.html"?>
-
+
<para>
</para>
@@ -610,7 +610,7 @@ indicate a place that may require attention for
multi-thread safety.
</section>
<section xml:id="coding_style.example"><info><title>By Example</title></info>
-
+
<literallayout class="normal">
This library is written to appropriate C++ coding standards. As such,
it is intended to precede the recommendations of the GNU Coding
@@ -1042,7 +1042,7 @@ indicate a place that may require attention for
multi-thread safety.
<section xml:id="contrib.design_notes" xreflabel="Design
Notes"><info><title>Design Notes</title></info>
<?dbhtml filename="source_design_notes.html"?>
-
+
<para>
</para>
diff --git a/libstdc++-v3/doc/xml/manual/appendix_free.xml
b/libstdc++-v3/doc/xml/manual/appendix_free.xml
index dd51eae8afc..0ce92c372d8 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_free.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_free.xml
@@ -1,4 +1,4 @@
-<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.free" xreflabel="Free">
<?dbhtml filename="appendix_free.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/appendix_porting.xml
b/libstdc++-v3/doc/xml/manual/appendix_porting.xml
index 8eb90d18745..8f3eca8d7b8 100644
--- a/libstdc++-v3/doc/xml/manual/appendix_porting.xml
+++ b/libstdc++-v3/doc/xml/manual/appendix_porting.xml
@@ -1,4 +1,4 @@
-<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<appendix xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.porting" xreflabel="Porting">
<?dbhtml filename="appendix_porting.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/atomics.xml
b/libstdc++-v3/doc/xml/manual/atomics.xml
index 5bd07585d69..0018212bc87 100644
--- a/libstdc++-v3/doc/xml/manual/atomics.xml
+++ b/libstdc++-v3/doc/xml/manual/atomics.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.atomics" xreflabel="Atomics">
<?dbhtml filename="atomics.html"?>
@@ -21,7 +21,7 @@
<!-- Sect1 01 : API -->
<section xml:id="std.atomics.api"><info><title>API Reference</title></info>
-
+
<para>
All items are declared in the standard header
diff --git a/libstdc++-v3/doc/xml/manual/auto_ptr.xml
b/libstdc++-v3/doc/xml/manual/auto_ptr.xml
index 2321b0f5029..f01e2d491b1 100644
--- a/libstdc++-v3/doc/xml/manual/auto_ptr.xml
+++ b/libstdc++-v3/doc/xml/manual/auto_ptr.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.util.memory.auto_ptr" xreflabel="auto_ptr">
<?dbhtml filename="auto_ptr.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
b/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
index 8d97c2193e7..cce553380e1 100644
--- a/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
+++ b/libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.appendix.porting.backwards" xreflabel="backwards">
<?dbhtml filename="backwards.html"?>
@@ -39,7 +39,7 @@ Committee couldn't include everything, and so a lot of those
<para>Portability notes and known implementation limitations are as
follows.</para>
<section xml:id="backwards.first.ios_base"><info><title>No
<code>ios_base</code></title></info>
-
+
<para> At least some older implementations don't have
<code>std::ios_base</code>, so you should use <code>std::ios::badbit</code>,
<code>std::ios::failbit</code> and <code>std::ios::eofbit</code> and
<code>std::ios::goodbit</code>.
</para>
@@ -93,7 +93,7 @@ considered replaced and rewritten.
</para>
<section xml:id="backwards.second.std"><info><title>Namespace
<code>std::</code> not supported</title></info>
-
+
<para>
Some care is required to support C++ compiler and or library
@@ -210,7 +210,7 @@ AC_DEFUN([AC_CXX_NAMESPACE_STD], [
<section xml:id="backwards.second.isspace"><info><title><code>isspace</code>
from <filename class="headerfile"><cctype></filename> is a macro
</title></info>
-
+
<para>
Glibc 2.0.x and 2.1.x define <filename
class="headerfile"><ctype.h></filename> functionality as macros
@@ -488,7 +488,7 @@ particular <quote>info iostream</quote>.
</section>
<section xml:id="backwards.second.wchar"><info><title>Little or no wide
character support</title></info>
-
+
<para>
Classes <classname>wstring</classname> and
<classname>char_traits<wchar_t></classname> are
@@ -497,7 +497,7 @@ particular <quote>info iostream</quote>.
</section>
<section xml:id="backwards.second.iostream_templates"><info><title>No
templatized iostreams</title></info>
-
+
<para>
Classes <classname>wfilebuf</classname> and
<classname>wstringstream</classname> are not supported.
diff --git a/libstdc++-v3/doc/xml/manual/bitmap_allocator.xml
b/libstdc++-v3/doc/xml/manual/bitmap_allocator.xml
index 82fc91278da..2b052d4a247 100644
--- a/libstdc++-v3/doc/xml/manual/bitmap_allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/bitmap_allocator.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.ext.allocator.bitmap" xreflabel="bitmap_allocator">
<?dbhtml filename="bitmap_allocator.html"?>
@@ -57,7 +57,7 @@
<section xml:id="bitmap.impl.free_list_store" xreflabel="Free List
Store"><info><title>Free List Store</title></info>
-
+
<para>
The Free List Store (referred to as FLS for the remaining part of this
@@ -122,7 +122,7 @@ else return false.</para></listitem>
</section>
<section xml:id="bitmap.impl.super_block" xreflabel="Super
Block"><info><title>Super Block</title></info>
-
+
<para>
A super block is the block of memory acquired from the FLS from
@@ -145,7 +145,7 @@ else return false.</para></listitem>
</section>
<section xml:id="bitmap.impl.super_block_data" xreflabel="Super Block
Data"><info><title>Super Block Data Layout</title></info>
-
+
<para>
Each Super Block will be of some size that is a multiple of the
number of Bits Per Block. Typically, this value is chosen as
@@ -221,7 +221,7 @@ else return false.</para></listitem>
</section>
<section xml:id="bitmap.impl.max_wasted" xreflabel="Max Wasted
Percentage"><info><title>Maximum Wasted Percentage</title></info>
-
+
<para>
This has nothing to do with the algorithm per-se,
@@ -262,7 +262,7 @@ For map/multimap: k = 12, and c = 4 (int and double), we
get: 37.524%
</section>
<section xml:id="bitmap.impl.allocate"
xreflabel="Allocate"><info><title><function>allocate</function></title></info>
-
+
<para>
The allocate function is specialized for single object allocation
@@ -368,7 +368,7 @@ single object allocations.
</section>
<section xml:id="bitmap.impl.deallocate"
xreflabel="Deallocate"><info><title><function>deallocate</function></title></info>
-
+
<para>
The deallocate function again is specialized for single objects ONLY.
For all n belonging to > 1, the operator delete is called without
@@ -412,10 +412,10 @@ single object allocations.
</section>
<section xml:id="bitmap.impl.questions"
xreflabel="Questions"><info><title>Questions</title></info>
-
+
<section xml:id="bitmap.impl.question.1" xreflabel="Question
1"><info><title>1</title></info>
-
+
<para>
Q1) The "Data Layout" section is
cryptic. I have no idea of what you are trying to say. Layout of what?
@@ -431,7 +431,7 @@ systems.
</section>
<section xml:id="bitmap.impl.question.2" xreflabel="Question
2"><info><title>2</title></info>
-
+
<para>
And since I just mentioned the
term `each bitmap', what in the world is meant by it? What does each
@@ -454,7 +454,7 @@ Block a bitmap as well?
</section>
<section xml:id="bitmap.impl.question.3" xreflabel="Question
3"><info><title>3</title></info>
-
+
<para>
How do the allocate and deallocate functions work in regard to
bitmaps?
@@ -495,7 +495,7 @@ Block a bitmap as well?
</section>
<section xml:id="bitmap.impl.locality"
xreflabel="Locality"><info><title>Locality</title></info>
-
+
<para>
Another issue would be whether to keep the all bitmaps in a
separate area in memory, or to keep them near the actual blocks
@@ -524,7 +524,7 @@ equivalent.</para></listitem>
</section>
<section xml:id="bitmap.impl.grow_policy" xreflabel="Grow
Policy"><info><title>Overhead and Grow Policy</title></info>
-
+
<para>
Expected overhead per block would be 1 bit in memory. Also, once
the address of the free list has been found, the cost for
diff --git a/libstdc++-v3/doc/xml/manual/build_hacking.xml
b/libstdc++-v3/doc/xml/manual/build_hacking.xml
index e9691bd375a..36f659cea4b 100644
--- a/libstdc++-v3/doc/xml/manual/build_hacking.xml
+++ b/libstdc++-v3/doc/xml/manual/build_hacking.xml
@@ -55,7 +55,7 @@ The <filename>configure</filename> file is a script generated
(via
<para>
- After the configure process is complete,
+ After the configure process is complete,
</para>
<screen>
@@ -92,7 +92,7 @@ in the build directory starts the build process. The
<literal>all</literal> targ
</figure>
<para>
- Regenerate all generated files by using the command
+ Regenerate all generated files by using the command
<command>autoreconf</command> at the top level of the libstdc++ source
directory.
</para>
diff --git a/libstdc++-v3/doc/xml/manual/codecvt.xml
b/libstdc++-v3/doc/xml/manual/codecvt.xml
index 1db941cf64d..d6158db7c75 100644
--- a/libstdc++-v3/doc/xml/manual/codecvt.xml
+++ b/libstdc++-v3/doc/xml/manual/codecvt.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.localization.facet.codecvt" xreflabel="codecvt">
<?dbhtml filename="codecvt.html"?>
@@ -114,7 +114,7 @@ particular.</para>
<section
xml:id="codecvt.design.wchar_t_size"><info><title><type>wchar_t</type>
Size</title></info>
-
+
<para>
The simple implementation detail of <type>wchar_t</type>'s size seems to
@@ -134,7 +134,7 @@ particular.</para>
</section>
<section xml:id="codecvt.design.unicode"><info><title>Support for
Unicode</title></info>
-
+
<para>
Probably the most frequently asked question about code conversion
is: "So dudes, what's the deal with Unicode strings?"
@@ -242,7 +242,7 @@ mechanism may be required.
</section>
<section xml:id="codecvt.design.issues"><info><title>Other
Issues</title></info>
-
+
<para>
In addition, multi-threaded and multi-locale environments also impact
the design and requirements for code conversions. In particular, they
diff --git a/libstdc++-v3/doc/xml/manual/concurrency.xml
b/libstdc++-v3/doc/xml/manual/concurrency.xml
index 0d3381f1a0e..62bb2aff87e 100644
--- a/libstdc++-v3/doc/xml/manual/concurrency.xml
+++ b/libstdc++-v3/doc/xml/manual/concurrency.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.concurrency" xreflabel="Concurrency">
<?dbhtml filename="concurrency.html"?>
@@ -25,7 +25,7 @@
<!-- Sect1 01 : API -->
<section xml:id="std.concurrency.api"><info><title>API Reference</title></info>
-
+
<para>
All items are declared in one of four standard header files.
diff --git a/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml
b/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml
index 663ae5eefb5..6499fda58c3 100644
--- a/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml
+++ b/libstdc++-v3/doc/xml/manual/concurrency_extensions.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.ext.concurrency" xreflabel="Concurrency Extensions">
<?dbhtml filename="ext_concurrency.html"?>
@@ -12,10 +12,10 @@
<section xml:id="manual.ext.concurrency.design"
xreflabel="Design"><info><title>Design</title></info>
-
+
<section xml:id="manual.ext.concurrency.design.threads" xreflabel="Threads
API"><info><title>Interface to Locks and Mutexes</title></info>
-
+
<para>The file <filename
class="headerfile"><ext/concurrence.h></filename>
contains all the higher-level
@@ -74,7 +74,7 @@ mutex and lock types defined in the header
</section>
<section xml:id="manual.ext.concurrency.design.atomics" xreflabel="Atomic
API"><info><title>Interface to Atomic Functions</title></info>
-
+
<para>
@@ -186,9 +186,9 @@ host hardware and operating system.
<section xml:id="manual.ext.concurrency.impl"
xreflabel="Implementation"><info><title>Implementation</title></info>
<?dbhtml filename="ext_concurrency_impl.html"?>
-
+
<section xml:id="manual.ext.concurrency.impl.atomic_fallbacks"
xreflabel="Atomic F"><info><title>Using Built-in Atomic Functions</title></info>
-
+
<para>The functions for atomic operations described above are either
implemented via compiler intrinsics (if the underlying host is
@@ -276,7 +276,7 @@ hardware, hand-crafted assembly is selected. This is the
case for the following
</section>
<section xml:id="manual.ext.concurrency.impl.thread"
xreflabel="Pthread"><info><title>Thread Abstraction</title></info>
-
+
<para>A thin layer above IEEE 1003.1 (i.e. pthreads) is used to abstract
the thread interface for GCC. This layer is called "gthread," and is
diff --git a/libstdc++-v3/doc/xml/manual/configure.xml
b/libstdc++-v3/doc/xml/manual/configure.xml
index 74d6db71ab4..b84ac426244 100644
--- a/libstdc++-v3/doc/xml/manual/configure.xml
+++ b/libstdc++-v3/doc/xml/manual/configure.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro.setup.configure" xreflabel="Configuring">
<?dbhtml filename="configure.html"?>
@@ -322,7 +322,7 @@
</listitem></varlistentry>
<varlistentry><term><code>--enable-libstdcxx-visibility</code></term>
- <listitem><para> In 4.2 and later, enables or disables visibility
+ <listitem><para> In 4.2 and later, enables or disables visibility
attributes. If enabled (as by default), and the compiler seems
capable of passing the simple sanity checks thrown at it, adjusts
items in namespace std, namespace std::tr1, namespace std::tr2,
@@ -348,10 +348,10 @@
<varlistentry><term><code>--enable-extern-template</code>[default]</term>
<listitem><para>Use extern template to pre-instantiate all required
- specializations for certain types defined in the standard libraries.
+ specializations for certain types defined in the standard libraries.
These types include <classname>string</classname> and dependents like
<classname>char_traits</classname>, the templatized IO classes,
- <classname>allocator</classname>, and others.
+ <classname>allocator</classname>, and others.
Disabling means that implicit
template generation will be used when compiling these types. By
default, this option is on. This option can change the library ABI.
diff --git a/libstdc++-v3/doc/xml/manual/containers.xml
b/libstdc++-v3/doc/xml/manual/containers.xml
index 6d568164b47..e5810fa5f31 100644
--- a/libstdc++-v3/doc/xml/manual/containers.xml
+++ b/libstdc++-v3/doc/xml/manual/containers.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.containers" xreflabel="Containers">
<?dbhtml filename="containers.html"?>
@@ -17,13 +17,13 @@
<!-- Sect1 01 : Sequences -->
<section xml:id="std.containers.sequences"
xreflabel="Sequences"><info><title>Sequences</title></info>
<?dbhtml filename="sequences.html"?>
-
+
<section xml:id="containers.sequences.list"
xreflabel="list"><info><title>list</title></info>
<?dbhtml filename="list.html"?>
-
+
<section xml:id="sequences.list.size" xreflabel="list::size() is
O(n)"><info><title>list::size() is O(n)</title></info>
-
+
<para>
Yes it is, at least using the <link linkend="manual.intro.using.abi">old
ABI</link>, and that's okay. This is a decision that we preserved
@@ -78,10 +78,10 @@
<!-- Sect1 02 : Associative -->
<section xml:id="std.containers.associative"
xreflabel="Associative"><info><title>Associative</title></info>
<?dbhtml filename="associative.html"?>
-
+
<section xml:id="containers.associative.insert_hints" xreflabel="Insertion
Hints"><info><title>Insertion Hints</title></info>
-
+
<para>
Section [23.1.2], Table 69, of the C++ standard lists this
function for all of the associative containers (map, set, etc):
@@ -189,9 +189,9 @@
<section xml:id="containers.associative.bitset"
xreflabel="bitset"><info><title>bitset</title></info>
<?dbhtml filename="bitset.html"?>
-
+
<section xml:id="associative.bitset.size_variable"
xreflabel="Variable"><info><title>Size Variable</title></info>
-
+
<para>
No, you cannot write code of the form
</para>
@@ -299,7 +299,7 @@
</section>
<section xml:id="associative.bitset.type_string" xreflabel="Type
String"><info><title>Type String</title></info>
-
+
<para>
</para>
<para>
@@ -452,10 +452,10 @@
<!-- Sect1 04 : Interacting with C -->
<section xml:id="std.containers.c" xreflabel="Interacting with
C"><info><title>Interacting with C</title></info>
<?dbhtml filename="containers_and_c.html"?>
-
+
<section xml:id="containers.c.vs_array" xreflabel="Containers vs.
Arrays"><info><title>Containers vs. Arrays</title></info>
-
+
<para>
You're writing some code and can't decide whether to use builtin
arrays or some kind of container. There are compelling reasons
diff --git a/libstdc++-v3/doc/xml/manual/ctype.xml
b/libstdc++-v3/doc/xml/manual/ctype.xml
index d0be7fb068a..55930c1751f 100644
--- a/libstdc++-v3/doc/xml/manual/ctype.xml
+++ b/libstdc++-v3/doc/xml/manual/ctype.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.localization.facet.ctype" xreflabel="ctype">
<?dbhtml filename="ctype.html"?>
@@ -15,7 +15,7 @@
<section
xml:id="facet.ctype.impl.spec"><info><title>Specializations</title></info>
-
+
<para>
For the required specialization <classname>codecvt<wchar_t, char,
mbstate_t></classname>,
diff --git a/libstdc++-v3/doc/xml/manual/debug.xml
b/libstdc++-v3/doc/xml/manual/debug.xml
index bb018569b39..7b60b497cfc 100644
--- a/libstdc++-v3/doc/xml/manual/debug.xml
+++ b/libstdc++-v3/doc/xml/manual/debug.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro.using.debug" xreflabel="Debugging Support">
<?dbhtml filename="debug.html"?>
@@ -210,7 +210,7 @@
</para>
<para>
- Two annotation macros are used to explain low-level synchronization
+ Two annotation macros are used to explain low-level synchronization
to race detectors:
<code>_GLIBCXX_SYNCHRONIZATION_HAPPENS_BEFORE()</code> and
<code> _GLIBCXX_SYNCHRONIZATION_HAPPENS_AFTER()</code>.
@@ -232,8 +232,8 @@
that are affected by the annotation macros, which can be done by
recompiling individual files.
Annotating <code>std::string</code> and <code>std::wstring</code>
- reference counting can be done by disabling extern templates (by defining
- <code>_GLIBCXX_EXTERN_TEMPLATE=-1</code>) or by rebuilding the
+ reference counting can be done by disabling extern templates (by defining
+ <code>_GLIBCXX_EXTERN_TEMPLATE=-1</code>) or by rebuilding the
<filename>src/string-inst.cc</filename> file.
Annotating the remaining atomic operations (at the time of writing these
are in <code>ios_base::Init::~Init</code>, <code>locale::_Impl</code>,
@@ -244,14 +244,14 @@
<para>
The approach described above is known to work with the following race
detection tools:
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://valgrind.org/docs/manual/drd-manual.html";>
DRD</link>,
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
- xlink:href="http://valgrind.org/docs/manual/hg-manual.html";>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
+ xlink:href="http://valgrind.org/docs/manual/hg-manual.html";>
Helgrind</link>, and
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
- xlink:href="https://github.com/google/sanitizers";>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
+ xlink:href="https://github.com/google/sanitizers";>
ThreadSanitizer</link> (this refers to ThreadSanitizer v1, not the
new "tsan" feature built-in to GCC itself).
</para>
diff --git a/libstdc++-v3/doc/xml/manual/debug_mode.xml
b/libstdc++-v3/doc/xml/manual/debug_mode.xml
index 570c17ba28a..883e8cb4f03 100644
--- a/libstdc++-v3/doc/xml/manual/debug_mode.xml
+++ b/libstdc++-v3/doc/xml/manual/debug_mode.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.ext.debug_mode" xreflabel="Debug Mode">
<?dbhtml filename="debug_mode.html"?>
@@ -13,7 +13,7 @@
<section xml:id="manual.ext.debug_mode.intro"
xreflabel="Intro"><info><title>Intro</title></info>
-
+
<para>
By default, libstdc++ is built with efficiency in mind, and
therefore performs little or no error checking that is not
@@ -59,7 +59,7 @@
<section xml:id="manual.ext.debug_mode.semantics"
xreflabel="Semantics"><info><title>Semantics</title></info>
<?dbhtml filename="debug_mode_semantics.html"?>
-
+
<para>
</para>
@@ -141,11 +141,11 @@ which always works correctly.
<section xml:id="manual.ext.debug_mode.using"
xreflabel="Using"><info><title>Using</title></info>
<?dbhtml filename="debug_mode_using.html"?>
-
+
<para>
</para>
<section xml:id="debug_mode.using.mode" xreflabel="Using
Mode"><info><title>Using the Debug Mode</title></info>
-
+
<para>To use the libstdc++ debug mode, compile your application with the
compiler flag <code>-D_GLIBCXX_DEBUG</code>. Note that this flag
@@ -163,7 +163,7 @@ which always works correctly.
</section>
<section xml:id="debug_mode.using.specific" xreflabel="Using
Specific"><info><title>Using a Specific Debug Container</title></info>
-
+
<para>When it is not feasible to recompile your entire application, or
only specific containers need checking, debugging containers are
available as GNU extensions. These debugging containers are
@@ -329,11 +329,11 @@ containers have additional debug capability.
<section xml:id="manual.ext.debug_mode.design"
xreflabel="Design"><info><title>Design</title></info>
<?dbhtml filename="debug_mode_design.html"?>
-
+
<para>
</para>
<section xml:id="debug_mode.design.goals"
xreflabel="Goals"><info><title>Goals</title></info>
-
+
<para>
</para>
<para> The libstdc++ debug mode replaces unsafe (but efficient) standard
@@ -448,7 +448,7 @@ containers have additional debug capability.
</section>
<section xml:id="debug_mode.design.methods"
xreflabel="Methods"><info><title>Methods</title></info>
-
+
<para>
</para>
<para>This section provides an overall view of the design of the
@@ -456,7 +456,7 @@ containers have additional debug capability.
decisions and the stated design goals.</para>
<section xml:id="debug_mode.design.methods.wrappers" xreflabel="Method
Wrapper"><info><title>The Wrapper Model</title></info>
-
+
<para>The libstdc++ debug mode uses a wrapper model where the
debugging versions of library components (e.g., iterators and
containers) form a layer on top of the release versions of the
@@ -479,7 +479,7 @@ containers have additional debug capability.
iterator from a different container.</para>
<section xml:id="debug_mode.design.methods.safe_iter" xreflabel="Method Safe
Iter"><info><title>Safe Iterators</title></info>
-
+
<para>Iterator wrappers provide a debugging layer over any iterator that
is attached to a particular container, and will manage the
information detailing the iterator's state (singular,
@@ -502,7 +502,7 @@ containers have additional debug capability.
</section>
<section xml:id="debug_mode.design.methods.safe_seq" xreflabel="Method Safe
Seq"><info><title>Safe Sequences (Containers)</title></info>
-
+
<para>Container wrappers provide a debugging layer over a particular
container type. Because containers vary greatly in the member
@@ -551,7 +551,7 @@ template<typename _Tp, typename _Allocator =
allocator<_Tp>
</section>
<section xml:id="debug_mode.design.methods.precond" xreflabel="Precondition
check"><info><title>Precondition Checking</title></info>
-
+
<para>The debug mode operates primarily by checking the preconditions of
all standard library operations that it supports. Preconditions that
are always checked (regardless of whether or not we are in debug
@@ -585,7 +585,7 @@ template<typename _Tp, typename _Allocator =
allocator<_Tp>
</section>
<section xml:id="debug_mode.design.methods.coexistence"
xreflabel="Coexistence"><info><title>Release- and debug-mode
coexistence</title></info>
-
+
<para>The libstdc++ debug mode is the first debug mode we know of that
is able to provide the "Per-use recompilation" (4) guarantee, that
allows release-compiled and debug-compiled code to be linked and
@@ -603,7 +603,7 @@ template<typename _Tp, typename _Allocator =
allocator<_Tp>
(namely, safe iterators).</para>
<section xml:id="methods.coexistence.compile"
xreflabel="Compile"><info><title>Compile-time coexistence of release- and
debug-mode components</title></info>
-
+
<para>Both the release-mode components and the debug-mode
components need to exist within a single translation unit so that
@@ -671,7 +671,7 @@ namespace std
<section xml:id="methods.coexistence.link"
xreflabel="Link"><info><title>Link- and run-time coexistence of release- and
debug-mode components</title></info>
-
+
<para>Because each component has a distinct and separate release and
debug implementation, there is no issue with link-time
@@ -854,7 +854,7 @@ test02()
</section>
<section xml:id="debug_mode.design.other"
xreflabel="Other"><info><title>Other Implementations</title></info>
-
+
<para>
</para>
<para> There are several existing implementations of debug modes for C++
diff --git a/libstdc++-v3/doc/xml/manual/diagnostics.xml
b/libstdc++-v3/doc/xml/manual/diagnostics.xml
index 08f576965d2..86737cc4d4d 100644
--- a/libstdc++-v3/doc/xml/manual/diagnostics.xml
+++ b/libstdc++-v3/doc/xml/manual/diagnostics.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.diagnostics" xreflabel="Diagnostics">
<?dbhtml filename="diagnostics.html"?>
@@ -16,10 +16,10 @@
<section xml:id="std.diagnostics.exceptions"
xreflabel="Exceptions"><info><title>Exceptions</title></info>
<?dbhtml filename="exceptions.html"?>
-
+
<section xml:id="std.diagnostics.exceptions.api"><info><title>API
Reference</title></info>
-
+
<para>
Most exception classes are defined in one of the standard headers
<filename class="headerfile"><exception></filename>,
@@ -52,12 +52,12 @@
<classname>std::string</classname> member. A full hierarchy can be
found in the source documentation.
</para>
-
+
<!-- Doxygen XML: api/group__exceptions.xml -->
-
+
</section>
<section xml:id="std.diagnostics.exceptions.data" xreflabel="Adding Data to
Exceptions"><info><title>Adding Data to
<classname>exception</classname></title></info>
-
+
<para>
The standard exception classes carry with them a single string as
data (usually describing what went wrong or where the 'throw' took
@@ -116,7 +116,7 @@
<section xml:id="std.diagnostics.concept_checking" xreflabel="Concept
Checking"><info><title>Concept Checking</title></info>
<?dbhtml filename="concept_checking.html"?>
-
+
<para>
In 1999, SGI added <quote>concept checkers</quote> to their
implementation of the STL: code which checked the template
diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
index 7db776794c2..723120808d7 100644
--- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
+++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.porting.doc" xreflabel="Documentation Hacking">
<?dbhtml filename="documentation_hacking.html"?>
@@ -43,7 +43,7 @@
reference. Although divergent, this conforms to the GNU Project
recommendations as long as the output is of sufficient quality,
as per
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://www.gnu.org/prep/standards/standards.html#Documentation";>
GNU Manuals</link>.
</para>
@@ -53,7 +53,7 @@
<info>
<title>Generating Documentation</title>
</info>
-
+
<para>
Certain Makefile rules are required by the GNU Coding
Standards. These standard rules generate HTML, PDF, XML, or man
@@ -130,7 +130,7 @@
</para>
</listitem>
</varlistentry>
-
+
<varlistentry>
<term>
<emphasis>make man</emphasis>
@@ -170,7 +170,7 @@
<filename>doc/libstdc++/libstdc++-manual.epub</filename>
</para>
</listitem>
- </varlistentry>
+ </varlistentry>
<varlistentry>
<term>
@@ -203,9 +203,9 @@
</section>
<section xml:id="doc.doxygen"><info><title>Doxygen</title></info>
-
+
<section xml:id="doxygen.prereq"><info><title>Prerequisites</title></info>
-
+
<table frame="all" xml:id="table.doxygen_prereq">
<title>Doxygen Prerequisites</title>
@@ -265,7 +265,7 @@
the <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://www.gnu.org/software/coreutils/";>GNU
coreutils</link>. (GNU versions of find, xargs, and possibly
sed and grep are used, just because the GNU versions make
- things very easy.)
+ things very easy.)
</para>
<para>
@@ -291,7 +291,7 @@
</section>
<section xml:id="doxygen.rules"><info><title>Generating the Doxygen
Files</title></info>
-
+
<para>
The following Makefile rules run Doxygen to generate HTML
docs, XML docs, XML docs as a single file, PDF docs, and the
@@ -346,7 +346,7 @@
<section xml:id="doxygen.debug">
<info><title>Debugging Generation</title></info>
-
+
<para>
Sometimes, mis-configuration of the pre-requisite tools can
lead to errors when attempting to build the
@@ -433,7 +433,7 @@
</section>
<section xml:id="doxygen.markup"><info><title>Markup</title></info>
-
+
<para>
In general, libstdc++ files should be formatted according to
@@ -446,7 +446,7 @@
<para>
Adding Doxygen markup to a file (informally called
<quote>doxygenating</quote>) is very simple. See the
- <link xmlns:xlink="http://www.w3.org/1999/xlink";
+ <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://www.doxygen.nl/download.html#latestman";>Doxygen
manual</link> for details.
We try to use a very-recent version of Doxygen.
@@ -649,11 +649,11 @@
</section>
<section xml:id="doc.docbook"><info><title>Docbook</title></info>
-
+
<section xml:id="docbook.prereq"><info><title>Prerequisites</title></info>
-
-
+
+
<table frame="all" xml:id="table.docbook_prereq">
<title>Docbook Prerequisites</title>
@@ -784,7 +784,7 @@
</section>
<section xml:id="docbook.rules"><info><title>Generating the DocBook
Files</title></info>
-
+
<para>
The following Makefile rules generate (in order): an HTML
@@ -939,7 +939,7 @@ make
<literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal>
<para>
This is equivalent to doing:
</para>
-
+
<screen>
<userinput>
xmllint --noout --valid <filename>xml/index.xml</filename>
@@ -961,7 +961,7 @@ make
<literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal>
</section>
<section xml:id="docbook.examples"><info><title>File Organization and
Basics</title></info>
-
+
<literallayout class="normal">
<emphasis>Which files are important</emphasis>
@@ -1027,7 +1027,7 @@ make
<literal>XSL_STYLE_DIR="/usr/share/xml/docbook/stylesheet/nwalsh"</literal>
</section>
<section xml:id="docbook.markup"><info><title>Markup By
Example</title></info>
-
+
<para>
Complete details on Docbook markup can be found in the
diff --git a/libstdc++-v3/doc/xml/manual/evolution.xml
b/libstdc++-v3/doc/xml/manual/evolution.xml
index 623d53e7faf..625202b9a06 100644
--- a/libstdc++-v3/doc/xml/manual/evolution.xml
+++ b/libstdc++-v3/doc/xml/manual/evolution.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.porting.api" xreflabel="api">
<?dbhtml filename="api.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/internals.xml
b/libstdc++-v3/doc/xml/manual/internals.xml
index 09407f86c24..5b3be2d1a84 100644
--- a/libstdc++-v3/doc/xml/manual/internals.xml
+++ b/libstdc++-v3/doc/xml/manual/internals.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="appendix.porting.internals" xreflabel="Portin Internals">
<?dbhtml filename="internals.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/intro.xml
b/libstdc++-v3/doc/xml/manual/intro.xml
index 4a5d25fa0d7..76e55980324 100644
--- a/libstdc++-v3/doc/xml/manual/intro.xml
+++ b/libstdc++-v3/doc/xml/manual/intro.xml
@@ -21,11 +21,11 @@
<!-- Chapter 01 : Status -->
<chapter xml:id="manual.intro.status"
xreflabel="Status"><info><title>Status</title></info>
<?dbhtml filename="status.html"?>
-
+
<!-- Section 01 : Implementation Status -->
<section xml:id="manual.intro.status.iso"
xreflabel="Status"><info><title>Implementation Status</title></info>
-
+
<!-- Section 01.1 : Status C++ 1998 -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; parse="xml"
href="status_cxx1998.xml">
@@ -63,7 +63,7 @@
<!-- Section 02 : License -->
<section xml:id="manual.intro.status.license"
xreflabel="License"><info><title>License</title></info>
<?dbhtml filename="license.html"?>
-
+
<para>
There are two licenses affecting GNU libstdc++: one for the code,
and one for the documentation.
@@ -75,7 +75,7 @@
</para>
<section xml:id="manual.intro.status.license.gpl" xreflabel="License
GPL"><info><title>The Code: GPL</title></info>
-
+
<para>
The source code is distributed under the <link
linkend="appendix.gpl-3.0">GNU General Public License version 3</link>,
@@ -166,7 +166,7 @@ requirements of the license of GCC.
</section>
<section xml:id="manual.intro.status.license.fdl" xreflabel="License
FDL"><info><title>The Documentation: GPL, FDL</title></info>
-
+
<para>
The documentation shipped with the library and made available over
@@ -195,10 +195,10 @@ requirements of the license of GCC.
<!-- Section 03 : Known Bugs -->
<section xml:id="manual.intro.status.bugs"
xreflabel="Bugs"><info><title>Bugs</title></info>
<?dbhtml filename="bugs.html"?>
-
+
<section xml:id="manual.intro.status.bugs.impl" xreflabel="Bugs
impl"><info><title>Implementation Bugs</title></info>
-
+
<para>
Information on known bugs, details on efforts to fix them, and
fixed bugs are all available as part of the <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://gcc.gnu.org/bugs/";>GCC bug tracking system</link>,
@@ -207,7 +207,7 @@ requirements of the license of GCC.
</section>
<section xml:id="manual.intro.status.bugs.iso" xreflabel="Bugs
iso"><info><title>Standard Bugs</title></info>
-
+
<para>
Everybody's got issues. Even the C++ Standard Library.
</para>
@@ -1285,7 +1285,7 @@ requirements of the license of GCC.
<!-- Chapter 02 : Setup -->
<chapter xml:id="manual.intro.setup"
xreflabel="Setup"><info><title>Setup</title></info>
<?dbhtml filename="setup.html"?>
-
+
<para>To transform libstdc++ sources into installed include files
and properly built binaries useful for linking to other software is
diff --git a/libstdc++-v3/doc/xml/manual/io.xml
b/libstdc++-v3/doc/xml/manual/io.xml
index 0c069b369e7..8380683561a 100644
--- a/libstdc++-v3/doc/xml/manual/io.xml
+++ b/libstdc++-v3/doc/xml/manual/io.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.io" xreflabel="Input and Output">
<?dbhtml filename="io.html"?>
@@ -17,7 +17,7 @@
<!-- Sect1 01 : Iostream Objects -->
<section xml:id="std.io.objects" xreflabel="IO Objects"><info><title>Iostream
Objects</title></info>
<?dbhtml filename="iostream_objects.html"?>
-
+
<para>To minimize the time you have to wait on the compiler, it's good to
only include the headers you really need. Many people simply include
@@ -180,10 +180,10 @@
<!-- Sect1 02 : Stream Buffers -->
<section xml:id="std.io.streambufs" xreflabel="Stream
Buffers"><info><title>Stream Buffers</title></info>
<?dbhtml filename="streambufs.html"?>
-
+
<section xml:id="io.streambuf.derived" xreflabel="Derived streambuf
Classes"><info><title>Derived streambuf Classes</title></info>
-
+
<para>
</para>
@@ -249,7 +249,7 @@
</section>
<section xml:id="io.streambuf.buffering"
xreflabel="Buffering"><info><title>Buffering</title></info>
-
+
<para>First, are you sure that you understand buffering? Particularly
the fact that C++ may not, in fact, have anything to do with it?
</para>
@@ -345,9 +345,9 @@
<!-- Sect1 03 : Memory-based Streams -->
<section xml:id="std.io.memstreams" xreflabel="Memory
Streams"><info><title>Memory Based Streams</title></info>
<?dbhtml filename="stringstreams.html"?>
-
+
<section xml:id="std.io.memstreams.compat" xreflabel="Compatibility
strstream"><info><title>Compatibility With strstream</title></info>
-
+
<para>
</para>
<para>Stringstreams (defined in the header <code><sstream></code>)
@@ -392,10 +392,10 @@
<!-- Sect1 04 : File-based Streams -->
<section xml:id="std.io.filestreams" xreflabel="File
Streams"><info><title>File Based Streams</title></info>
<?dbhtml filename="fstreams.html"?>
-
+
<section xml:id="std.io.filestreams.copying_a_file" xreflabel="Copying a
File"><info><title>Copying a File</title></info>
-
+
<para>
</para>
@@ -461,7 +461,7 @@
</section>
<section xml:id="std.io.filestreams.binary" xreflabel="Binary Input and
Output"><info><title>Binary Input and Output</title></info>
-
+
<para>
</para>
<para>The first and most important thing to remember about binary I/O is
@@ -595,11 +595,11 @@
<!-- Sect1 03 : Interacting with C -->
<section xml:id="std.io.c" xreflabel="Interacting with
C"><info><title>Interacting with C</title></info>
<?dbhtml filename="io_and_c.html"?>
-
+
<section xml:id="std.io.c.FILE" xreflabel="Using FILE* and file
descriptors"><info><title>Using FILE* and file descriptors</title></info>
-
+
<para>
See the <link linkend="manual.ext.io">extensions</link> for using
<type>FILE</type> and <type>file descriptors</type> with
@@ -609,7 +609,7 @@
</section>
<section xml:id="std.io.c.sync" xreflabel="Performance
Issues"><info><title>Performance</title></info>
-
+
<para>
Pathetic Performance? Ditch C.
</para>
diff --git a/libstdc++-v3/doc/xml/manual/iterators.xml
b/libstdc++-v3/doc/xml/manual/iterators.xml
index aab26b92e40..d0b75084e05 100644
--- a/libstdc++-v3/doc/xml/manual/iterators.xml
+++ b/libstdc++-v3/doc/xml/manual/iterators.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.iterators" xreflabel="Iterators">
<?dbhtml filename="iterators.html"?>
@@ -16,10 +16,10 @@
<!-- Sect1 01 : Predefined -->
<section xml:id="std.iterators.predefined"
xreflabel="Predefined"><info><title>Predefined</title></info>
-
+
<section xml:id="iterators.predefined.vs_pointers" xreflabel="Versus
Pointers"><info><title>Iterators vs. Pointers</title></info>
-
+
<para>
The following
FAQ <link linkend="faq.iterator_as_pod">entry</link> points out that
@@ -66,7 +66,7 @@ classes.
</section>
<section xml:id="iterators.predefined.end" xreflabel="end() Is One Past the
End"><info><title>One Past the End</title></info>
-
+
<para>This starts off sounding complicated, but is actually very easy,
especially towards the end. Trust me.
diff --git a/libstdc++-v3/doc/xml/manual/locale.xml
b/libstdc++-v3/doc/xml/manual/locale.xml
index c0552b4aa48..7f6a7e70688 100644
--- a/libstdc++-v3/doc/xml/manual/locale.xml
+++ b/libstdc++-v3/doc/xml/manual/locale.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.localization.locales.locale" xreflabel="Locale">
<info><title>locale</title>
@@ -106,7 +106,7 @@ portability is an issue.
<section xml:id="locale.impl.c"><info><title>Interacting with "C"
locales</title></info>
-
+
<itemizedlist>
<listitem>
diff --git a/libstdc++-v3/doc/xml/manual/localization.xml
b/libstdc++-v3/doc/xml/manual/localization.xml
index d05ca4d7dca..22d861ced40 100644
--- a/libstdc++-v3/doc/xml/manual/localization.xml
+++ b/libstdc++-v3/doc/xml/manual/localization.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.localization" xreflabel="Localization">
<?dbhtml filename="localization.html"?>
@@ -17,7 +17,7 @@
<!-- Section 01 : Locale -->
<section xml:id="std.localization.locales"
xreflabel="Locales"><info><title>Locales</title></info>
<?dbhtml filename="locales.html"?>
-
+
<!-- Section 01 : locale -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; parse="xml"
href="locale.xml">
@@ -27,7 +27,7 @@
<!-- Section 02 : Facet -->
<section xml:id="std.localization.facet"
xreflabel="Facets"><info><title>Facets</title></info>
<?dbhtml filename="facets.html"?>
-
+
<!-- Section 01 : ctype -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"; parse="xml"
href="ctype.xml">
diff --git a/libstdc++-v3/doc/xml/manual/messages.xml
b/libstdc++-v3/doc/xml/manual/messages.xml
index 12ebd443508..b1bc4b76f07 100644
--- a/libstdc++-v3/doc/xml/manual/messages.xml
+++ b/libstdc++-v3/doc/xml/manual/messages.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.localization.facet.messages" xreflabel="Messages">
<?dbhtml filename="messages.html"?>
@@ -116,7 +116,7 @@ A couple of notes on the standard.
First, why is <code>messages_base::catalog</code> specified as a typedef
to int? This makes sense for implementations that use
<code>catopen</code> and define <code>nl_catd</code> as int, but not for
-others. Fortunately, it's not heavily used and so only a minor irritant.
+others. Fortunately, it's not heavily used and so only a minor irritant.
This has been reported as a possible defect in the standard (LWG 2028).
</para>
@@ -159,7 +159,7 @@ other, explicitly named locales.
<section xml:id="messages.impl.models"><info><title>Models</title></info>
-
+
<para>
This is a relatively simple class, on the face of it. The standard
specifies very little in concrete terms, so generic
@@ -227,7 +227,7 @@ model.
</section>
<section xml:id="messages.impl.gnu"><info><title>The GNU Model</title></info>
-
+
<para>
The messages facet, because it is retrieving and converting
diff --git a/libstdc++-v3/doc/xml/manual/mt_allocator.xml
b/libstdc++-v3/doc/xml/manual/mt_allocator.xml
index e89a0145490..93504a7d711 100644
--- a/libstdc++-v3/doc/xml/manual/mt_allocator.xml
+++ b/libstdc++-v3/doc/xml/manual/mt_allocator.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.ext.allocator.mt" xreflabel="mt allocator">
<?dbhtml filename="mt_allocator.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/numerics.xml
b/libstdc++-v3/doc/xml/manual/numerics.xml
index cc2615390f2..bb1d45d6b3b 100644
--- a/libstdc++-v3/doc/xml/manual/numerics.xml
+++ b/libstdc++-v3/doc/xml/manual/numerics.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.numerics" xreflabel="Numerics">
<?dbhtml filename="numerics.html"?>
@@ -17,11 +17,11 @@
<!-- Sect1 01 : Complex -->
<section xml:id="std.numerics.complex"
xreflabel="complex"><info><title>Complex</title></info>
<?dbhtml filename="complex.html"?>
-
+
<para>
</para>
<section xml:id="numerics.complex.processing" xreflabel="complex
Processing"><info><title>complex Processing</title></info>
-
+
<para>
</para>
<para>Using <code>complex<></code> becomes even more comple- er,
sorry,
@@ -52,7 +52,7 @@
<!-- Sect1 02 : Generalized Operations -->
<section xml:id="std.numerics.generalized_ops" xreflabel="Generalized
Ops"><info><title>Generalized Operations</title></info>
<?dbhtml filename="generalized_numeric_operations.html"?>
-
+
<para>
</para>
@@ -95,10 +95,10 @@
<!-- Sect1 03 : Interacting with C -->
<section xml:id="std.numerics.c" xreflabel="Interacting with
C"><info><title>Interacting with C</title></info>
<?dbhtml filename="numerics_and_c.html"?>
-
+
<section xml:id="numerics.c.array" xreflabel="Numerics vs.
Arrays"><info><title>Numerics vs. Arrays</title></info>
-
+
<para>One of the major reasons why FORTRAN can chew through numbers so well
is that it is defined to be free of pointer aliasing, an assumption
@@ -121,7 +121,7 @@
</section>
<section xml:id="numerics.c.c99"
xreflabel="C99"><info><title>C99</title></info>
-
+
<para>In addition to the other topics on this page, we'll note here some
of the C99 features that appear in libstdc++.
diff --git a/libstdc++-v3/doc/xml/manual/parallel_mode.xml
b/libstdc++-v3/doc/xml/manual/parallel_mode.xml
index ab7d2f2b56b..cabb9d76a4c 100644
--- a/libstdc++-v3/doc/xml/manual/parallel_mode.xml
+++ b/libstdc++-v3/doc/xml/manual/parallel_mode.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.ext.parallel_mode" xreflabel="Parallel Mode">
<?dbhtml filename="parallel_mode.html"?>
@@ -40,7 +40,7 @@ specific compiler flag.
</note>
<section xml:id="manual.ext.parallel_mode.intro"
xreflabel="Intro"><info><title>Intro</title></info>
-
+
<para>The following library components in the include
<filename class="headerfile">numeric</filename> are included in the parallel
mode:</para>
@@ -91,7 +91,7 @@ specific compiler flag.
<section xml:id="manual.ext.parallel_mode.semantics"
xreflabel="Semantics"><info><title>Semantics</title></info>
<?dbhtml filename="parallel_mode_semantics.html"?>
-
+
<para> The parallel mode STL algorithms are currently not exception-safe,
i.e. user-defined functors must not throw exceptions.
@@ -109,10 +109,10 @@ It might work with other compilers, though.</para>
<section xml:id="manual.ext.parallel_mode.using"
xreflabel="Using"><info><title>Using</title></info>
<?dbhtml filename="parallel_mode_using.html"?>
-
+
<section xml:id="parallel_mode.using.prereq_flags"><info><title>Prerequisite
Compiler Flags</title></info>
-
+
<para>
Any use of parallel functionality requires additional compiler
@@ -140,7 +140,7 @@ In addition, hardware that supports atomic operations and a
compiler
</section>
<section xml:id="parallel_mode.using.parallel_mode"><info><title>Using
Parallel Mode</title></info>
-
+
<para>
To use the libstdc++ parallel mode, compile your application with
@@ -165,7 +165,7 @@ In addition, hardware that supports atomic operations and a
compiler
</section>
<section xml:id="parallel_mode.using.specific"><info><title>Using Specific
Parallel Components</title></info>
-
+
<para>When it is not feasible to recompile your entire application, or
only specific algorithms need to be parallel-aware, individual
@@ -476,11 +476,11 @@ flags for atomic operations.)
<section xml:id="manual.ext.parallel_mode.design"
xreflabel="Design"><info><title>Design</title></info>
<?dbhtml filename="parallel_mode_design.html"?>
-
+
<para>
</para>
<section xml:id="parallel_mode.design.intro"
xreflabel="Intro"><info><title>Interface Basics</title></info>
-
+
<para>
All parallel algorithms are intended to have signatures that are
@@ -549,11 +549,11 @@ overload is therefore missing.
</section>
<section xml:id="parallel_mode.design.tuning"
xreflabel="Tuning"><info><title>Configuration and Tuning</title></info>
-
+
<section xml:id="parallel_mode.design.tuning.omp" xreflabel="OpenMP
Environment"><info><title>Setting up the OpenMP Environment</title></info>
-
+
<para>
Several aspects of the overall runtime environment can be manipulated
@@ -598,7 +598,7 @@ documentation for more information.
</section>
<section xml:id="parallel_mode.design.tuning.compile" xreflabel="Compile
Switches"><info><title>Compile Time Switches</title></info>
-
+
<para>
To force an algorithm to execute sequentially, even though parallelism
@@ -675,7 +675,7 @@ merging. The quicksort options cannot be used for
<code>stable_sort</code>.
</section>
<section xml:id="parallel_mode.design.tuning.settings"
xreflabel="_Settings"><info><title>Run Time Settings and Defaults</title></info>
-
+
<para>
The default parallelization strategy, the choice of specific algorithm
@@ -769,7 +769,7 @@ int main()
</section>
<section xml:id="parallel_mode.design.impl"
xreflabel="Impl"><info><title>Implementation Namespaces</title></info>
-
+
<para> One namespace contain versions of code that are always
explicitly sequential:
@@ -803,7 +803,7 @@ the generated source documentation.
<section xml:id="manual.ext.parallel_mode.test"
xreflabel="Testing"><info><title>Testing</title></info>
<?dbhtml filename="parallel_mode_test.html"?>
-
+
<para>
Both the normal conformance and regression tests and the
diff --git a/libstdc++-v3/doc/xml/manual/policy_data_structures.xml
b/libstdc++-v3/doc/xml/manual/policy_data_structures.xml
index 107018043ae..3e598105f7e 100644
--- a/libstdc++-v3/doc/xml/manual/policy_data_structures.xml
+++ b/libstdc++-v3/doc/xml/manual/policy_data_structures.xml
@@ -3003,7 +3003,7 @@
</textobject>
</mediaobject>
</figure>
-
+
<para>Let U be a domain (e.g., the integers, or the
strings of 3 characters). A hash-table algorithm needs to map
elements of U "uniformly" into the range [0,..., m -
@@ -3179,7 +3179,7 @@
0</subscript><superscript>t - 1</superscript>
s<subscript>i</subscript> a<superscript>i</superscript> mod m
</mathphrase>
</equation>
-
+
<para>where a is some non-negative integral value. This is
the standard string-hashing function used in SGI's
@@ -3202,7 +3202,7 @@
</title>
<mathphrase>
f<subscript>2</subscript>(s, m) = ∑ <subscript>i
- = 0</subscript><superscript>k - 1</superscript>
s<subscript>i</subscript> a<superscript>i</superscript> mod m
+ = 0</subscript><superscript>k - 1</superscript>
s<subscript>i</subscript> a<superscript>i</superscript> mod m
</mathphrase>
</equation>
@@ -3278,7 +3278,7 @@
</textobject>
</mediaobject>
</figure>
-
+
<para>If <classname>cc_hash_table</classname>'s
hash-functor, <classname>Hash_Fn</classname> is instantiated by
<classname>null_type</classname> , then <classname>Comb_Hash_Fn</classname> is
taken to be
a ranged-hash function. The graphic below shows an
<function>insert</function> sequence
@@ -3298,7 +3298,7 @@
</textobject>
</mediaobject>
</figure>
-
+
</section>
<section xml:id="hash_policies.implementation.probe">
@@ -3459,7 +3459,7 @@
Probability of Probe Sequence of Length k
</title>
<mathphrase>
- p<subscript>1</subscript> =
+ p<subscript>1</subscript> =
</mathphrase>
</equation>
@@ -3486,7 +3486,7 @@
Probability Probe Sequence in Some Bin
</title>
<mathphrase>
- P( exists<subscript>i</subscript> l<subscript>i</subscript> ≥ k
) =
+ P( exists<subscript>i</subscript> l<subscript>i</subscript> ≥ k
) =
</mathphrase>
</equation>
@@ -3640,7 +3640,7 @@
<para>The graphic below gives an overall picture of the
resize-related
classes. <classname>basic_hash_table</classname>
is parametrized by <classname>Resize_Policy</classname>, which it
subclasses
- publicly. This class is currently instantiated only by
<classname>hash_standard_resize_policy</classname>.
+ publicly. This class is currently instantiated only by
<classname>hash_standard_resize_policy</classname>.
<classname>hash_standard_resize_policy</classname>
itself is parametrized by <classname>Trigger_Policy</classname>
and
<classname>Size_Policy</classname>. Currently,
<classname>Trigger_Policy</classname> is
@@ -3917,7 +3917,7 @@
</textobject>
</mediaobject>
</figure>
-
+
<para>Supporting such trees is difficult for a number of
reasons:</para>
@@ -3983,7 +3983,7 @@
node_end() const;
node_iterator
- node_end();
+ node_end();
</programlisting>
<para>The first pairs return node iterators corresponding to the
@@ -4026,7 +4026,7 @@
<para><classname>node_update</classname> must also define the
following method
for restoring node invariants:</para>
<programlisting>
- void
+ void
operator()(node_iterator nd_it, const_node_iterator end_nd_it)
</programlisting>
@@ -4172,7 +4172,7 @@
</section>
- </section>
+ </section>
<section xml:id="container.tree.details.split">
<info><title>Split and Join</title></info>
@@ -4247,8 +4247,8 @@
currently illegal.</para>
<para>Following is a description of a (PATRICIA) trie
- (this implementation follows <xref linkend="biblio.okasaki98mereable"/>
and
- <xref linkend="biblio.filliatre2000ptset"/>).
+ (this implementation follows <xref linkend="biblio.okasaki98mereable"/>
and
+ <xref linkend="biblio.filliatre2000ptset"/>).
</para>
<para>A (PATRICIA) trie is similar to a tree, but with the
@@ -4615,7 +4615,7 @@
which unconditionally move an accessed element to the front of
the list. The latter type is very useful in this library,
since there is no need to associate metadata with each element.
- (See <xref linkend="biblio.andrew04mtf"/>
+ (See <xref linkend="biblio.andrew04mtf"/>
</para>
</section>
@@ -4717,7 +4717,7 @@
<classname>binomial_heap_tag</classname>,
<classname>rc_binomial_heap_tag</classname>,
or <classname>thin_heap_tag</classname>,
- specifies, respectively,
+ specifies, respectively,
an underlying pairing heap (<xref linkend="biblio.fredman86pairing"/>),
binary heap (<xref linkend="biblio.clrs2001"/>),
binomial heap (<xref linkend="biblio.clrs2001"/>),
@@ -4819,7 +4819,7 @@
assert(p.top() == 3);
</programlisting>
-
+
<para>It should be noted that an alternative design could embed an
associative container in a priority queue. Could, but most
probably should not. To begin with, it should be noted that one
@@ -4944,7 +4944,7 @@
<para>Of course, one can use any order-preserving associative
container as a priority queue, as in the graphic above label C,
possibly by creating an adapter class
- over the associative container (much as
+ over the associative container (much as
<classname>std::priority_queue</classname> can adapt
<classname>std::vector</classname>).
This has the advantage that no cross-referencing is necessary
at all; the priority queue itself is an associative container.
@@ -4969,7 +4969,7 @@
types. <classname>__gnu_pbds::priority_queue</classname>
publicly defines <classname>container_category</classname> as one of
the tags. Given any
container <classname>Cntnr</classname>, the tag of the underlying
- data structure can be found via <classname>typename
+ data structure can be found via <classname>typename
Cntnr::container_category</classname>; this is one of the possible
tags shown in the graphic below.
</para>
@@ -4994,7 +4994,7 @@
container.</para>
<para>To find if a container might throw if two of its objects are
- joined, one can use
+ joined, one can use
<programlisting>
container_traits<Cntnr>::split_join_can_throw
</programlisting>
diff --git a/libstdc++-v3/doc/xml/manual/prerequisites.xml
b/libstdc++-v3/doc/xml/manual/prerequisites.xml
index aa677647555..22e90a7e79d 100644
--- a/libstdc++-v3/doc/xml/manual/prerequisites.xml
+++ b/libstdc++-v3/doc/xml/manual/prerequisites.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro.setup.prereq" xreflabel="Prerequisites">
<?dbhtml filename="prerequisites.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/shared_ptr.xml
b/libstdc++-v3/doc/xml/manual/shared_ptr.xml
index 24e275e95eb..06fc662e6ef 100644
--- a/libstdc++-v3/doc/xml/manual/shared_ptr.xml
+++ b/libstdc++-v3/doc/xml/manual/shared_ptr.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.util.memory.shared_ptr" xreflabel="shared_ptr">
<?dbhtml filename="shared_ptr.html"?>
@@ -60,7 +60,7 @@ technique known as type erasure.
<section xml:id="shared_ptr.hier"><info><title>Class Hierarchy</title></info>
-
+
<para>
A <classname>shared_ptr<T></classname> contains a pointer of
@@ -156,7 +156,7 @@ deprecated in C++11 mode.
</section>
<section xml:id="shared_ptr.thread"><info><title>Thread Safety</title></info>
-
+
<para>
The
<link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://www.boost.org/libs/smart_ptr/shared_ptr.htm#ThreadSafety";>Thread
@@ -214,7 +214,7 @@ Policy below for details.
</section>
<section xml:id="shared_ptr.policy"><info><title>Selecting Lock
Policy</title></info>
-
+
<para>
</para>
@@ -351,7 +351,7 @@ be private.
<section xml:id="shared_ptr.examples"><info><title>Examples</title></info>
-
+
<para>
Examples of use can be found in the testsuite, under
<filename
class="directory">testsuite/tr1/2_general_utilities/shared_ptr</filename>,
@@ -362,7 +362,7 @@ be private.
</section>
<section xml:id="shared_ptr.issues"><info><title>Unresolved
Issues</title></info>
-
+
<para>
The <emphasis><classname>shared_ptr</classname> atomic access</emphasis>
clause in the C++11 standard is not implemented in GCC.
diff --git a/libstdc++-v3/doc/xml/manual/spine.xml
b/libstdc++-v3/doc/xml/manual/spine.xml
index 4db3037ac4d..34daa33344c 100644
--- a/libstdc++-v3/doc/xml/manual/spine.xml
+++ b/libstdc++-v3/doc/xml/manual/spine.xml
@@ -1,4 +1,4 @@
-<book xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<book xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual" xreflabel="Manual">
<?dbhtml dir="manual"?>
<?dbhtml filename="index.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
index b9e415d21ac..021cb6394a7 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr1.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="status.iso.tr1" xreflabel="Status C++ TR1">
<?dbhtml filename="status_iso_cxxtr1.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
index 92d892da8ac..139b94442e8 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxxtr24733.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="status.iso.tr24733" xreflabel="Status C++ TR24733">
<?dbhtml filename="status_iso_cxxtr24733.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/strings.xml
b/libstdc++-v3/doc/xml/manual/strings.xml
index 1c7ab4ca706..e9d4c8ce347 100644
--- a/libstdc++-v3/doc/xml/manual/strings.xml
+++ b/libstdc++-v3/doc/xml/manual/strings.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.strings" xreflabel="Strings">
<?dbhtml filename="strings.html"?>
@@ -16,10 +16,10 @@
<!-- Sect1 02 : String Classes -->
<section xml:id="std.strings.string" xreflabel="string"><info><title>String
Classes</title></info>
-
+
<section xml:id="strings.string.simple" xreflabel="Simple
Transformations"><info><title>Simple Transformations</title></info>
-
+
<para>
Here are Standard, simple, and portable ways to perform common
transformations on a <code>string</code> instance, such as
@@ -115,7 +115,7 @@
</section>
<section xml:id="strings.string.case" xreflabel="Case
Sensitivity"><info><title>Case Sensitivity</title></info>
-
+
<para>
</para>
@@ -166,7 +166,7 @@
</section>
<section xml:id="strings.string.character_types" xreflabel="Arbitrary
Characters"><info><title>Arbitrary Character Types</title></info>
-
+
<para>
</para>
@@ -238,7 +238,7 @@
</section>
<section xml:id="strings.string.token"
xreflabel="Tokenizing"><info><title>Tokenizing</title></info>
-
+
<para>
</para>
<para>The Standard C (and C++) function <code>strtok()</code> leaves a lot
to
@@ -337,7 +337,7 @@ stringtok(Container &container, string const &in,
</section>
<section xml:id="strings.string.shrink" xreflabel="Shrink to
Fit"><info><title>Shrink to Fit</title></info>
-
+
<para>
</para>
<para>From GCC 3.4 calling <code>s.reserve(res)</code> on a
@@ -365,7 +365,7 @@ stringtok(Container &container, string const &in,
</section>
<section xml:id="strings.string.Cstring" xreflabel="CString
(MFC)"><info><title>CString (MFC)</title></info>
-
+
<para>
</para>
diff --git a/libstdc++-v3/doc/xml/manual/support.xml
b/libstdc++-v3/doc/xml/manual/support.xml
index da8fed0e015..f4b41664f60 100644
--- a/libstdc++-v3/doc/xml/manual/support.xml
+++ b/libstdc++-v3/doc/xml/manual/support.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.support" xreflabel="Support">
<?dbhtml filename="support.html"?>
diff --git a/libstdc++-v3/doc/xml/manual/test.xml
b/libstdc++-v3/doc/xml/manual/test.xml
index 19bc9e81ff3..ee00b06e385 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro.setup.test" xreflabel="Testing">
<?dbhtml filename="test.html"?>
@@ -235,7 +235,7 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
<section xml:id="test.run.basic"><info><title>Basic</title></info>
-
+
<para>
You can check the status of the build without installing it
@@ -275,7 +275,7 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
</section>
<section xml:id="test.run.variations"><info><title>Variations</title></info>
-
+
<para>
There are several options for running tests, including testing
the regression tests, testing a subset of the regression tests,
@@ -552,7 +552,7 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
</section>
<section
xml:id="test.run.permutations"><info><title>Permutations</title></info>
-
+
<para>
The tests will be compiled with a set of default compiler flags defined
by the
diff --git a/libstdc++-v3/doc/xml/manual/test_policy_data_structures.xml
b/libstdc++-v3/doc/xml/manual/test_policy_data_structures.xml
index ea35efa22b9..cb5b016569a 100644
--- a/libstdc++-v3/doc/xml/manual/test_policy_data_structures.xml
+++ b/libstdc++-v3/doc/xml/manual/test_policy_data_structures.xml
@@ -3835,7 +3835,7 @@
<!-- 01 <a href="multimap_text_find_timing_test_small"> -->
<section xml:id="performance.multimap.text_find_small">
<info><title>
- Text <function>find</function> with Small Secondary-to-Primary Key
Ratios
+ Text <function>find</function> with Small Secondary-to-Primary Key
Ratios
</title></info>
<para></para>
@@ -4299,7 +4299,7 @@
<!-- 02 <a href="multimap_text_find_timing_test_large"> -->
<section xml:id="performance.multimap.text_find_large">
<info><title>
- Text <function>find</function> with Large Secondary-to-Primary Key
Ratios
+ Text <function>find</function> with Large Secondary-to-Primary Key
Ratios
</title></info>
<para></para>
diff --git a/libstdc++-v3/doc/xml/manual/using.xml
b/libstdc++-v3/doc/xml/manual/using.xml
index 60c5238555e..24543e9526e 100644
--- a/libstdc++-v3/doc/xml/manual/using.xml
+++ b/libstdc++-v3/doc/xml/manual/using.xml
@@ -1,10 +1,10 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro.using" xreflabel="Using">
<info><title>Using</title></info>
<?dbhtml filename="using.html"?>
<section xml:id="manual.intro.using.flags"
xreflabel="Flags"><info><title>Command Options</title></info>
-
+
<para>
The set of features available in the GNU C++ library is shaped by
several <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Invoking-GCC.html";>GCC
@@ -107,7 +107,7 @@
<entry><literal>-fopenmp</literal></entry>
<entry>For <link linkend="manual.ext.parallel_mode">parallel</link>
mode.</entry>
</row>
-
+
<row>
<entry><literal>-ltbb</literal></entry>
<entry>Linking to tbb (Thread Building Blocks) is required for use of the
@@ -115,7 +115,7 @@
<filename class="headerfile"><execution></filename>.
</entry>
</row>
-
+
</tbody>
</tgroup>
@@ -125,10 +125,10 @@
<section xml:id="manual.intro.using.headers"
xreflabel="Headers"><info><title>Headers</title></info>
<?dbhtml filename="using_headers.html"?>
-
+
<section xml:id="manual.intro.using.headers.all" xreflabel="Header
Files"><info><title>Header Files</title></info>
-
+
<para>
The C++ standard specifies the entire set of header files that
@@ -523,7 +523,7 @@ compilation errors, but will not define anything.
<para>
<xref linkend="table.libfundts_headers"/>,
-shows the additional include files define by the C++ Extensions for
+shows the additional include files define by the C++ Extensions for
Library Fundamentals Technical Specification, ISO/IEC TS 19568.
These are available in C++14 and later compilation modes.
Including these headers in earlier modes will not result in
@@ -822,7 +822,7 @@ compiler supports scalar decimal floating-point types
defined via
</section>
<section xml:id="manual.intro.using.headers.mixing" xreflabel="Mixing
Headers"><info><title>Mixing Headers</title></info>
-
+
<para> A few simple rules.
</para>
@@ -865,7 +865,7 @@ same translation unit:
</section>
<section xml:id="manual.intro.using.headers.cheaders" xreflabel="C Headers
and"><info><title>The C Headers and <code>namespace std</code></title></info>
-
+
<para>
The standard specifies that if one includes the C-style header
@@ -892,7 +892,7 @@ and <code>std::sinl</code>.
</section>
<section xml:id="manual.intro.using.headers.pre" xreflabel="Precompiled
Headers"><info><title>Precompiled Headers</title></info>
-
+
<para>There are three base header files that are provided. They can be
@@ -973,7 +973,7 @@ g++ -Winvalid-pch -I. -include stdc++.h -H -g -O2 hello.cc
-o test.exe
<section xml:id="manual.intro.using.macros"
xreflabel="Macros"><info><title>Macros</title></info>
<?dbhtml filename="using_macros.html"?>
-
+
<para>
All library macros begin with <code>_GLIBCXX_</code>.
@@ -1290,10 +1290,10 @@ g++ -Winvalid-pch -I. -include stdc++.h -H -g -O2
hello.cc -o test.exe
<section xml:id="manual.intro.using.namespaces"
xreflabel="Namespaces"><info><title>Namespaces</title></info>
<?dbhtml filename="using_namespaces.html"?>
-
+
<section xml:id="manual.intro.using.namespaces.all" xreflabel="Available
Namespaces"><info><title>Available Namespaces</title></info>
-
+
@@ -1334,7 +1334,7 @@ details that are not intended for users to refer to
directly, these include
</section>
<section xml:id="manual.intro.using.namespaces.std" xreflabel="namespace
std"><info><title>namespace std</title></info>
-
+
<para>
@@ -1360,7 +1360,7 @@ cases where the qualified verbiage becomes unwieldy.)
</section>
<section xml:id="manual.intro.using.namespaces.comp" xreflabel="Using
Namespace Composition"><info><title>Using Namespace Composition</title></info>
-
+
<para>
Best practice in programming suggests sequestering new data or
@@ -1407,10 +1407,10 @@ namespace gtk
<section xml:id="manual.intro.using.linkage"
xreflabel="Linkage"><info><title>Linking</title></info>
<?dbhtml filename="using_dynamic_or_shared.html"?>
-
+
<section xml:id="manual.intro.using.linkage.freestanding"
xreflabel="Freestanding"><info><title>Almost Nothing</title></info>
-
+
<para>
Or as close as it gets: freestanding. This is a minimal
configuration, with only partial support for the standard
@@ -1514,7 +1514,7 @@ namespace gtk
</section>
<section xml:id="manual.intro.using.linkage.dynamic" xreflabel="Dynamic
and Shared"><info><title>Finding Dynamic or Shared Libraries</title></info>
-
+
<para>
If the only library built is the static library
@@ -1638,7 +1638,7 @@ A quick read of the relevant part of the GCC
<section xml:id="manual.intro.using.concurrency"
xreflabel="Concurrency"><info><title>Concurrency</title></info>
<?dbhtml filename="using_concurrency.html"?>
-
+
<para>This section discusses issues surrounding the proper compilation
of multithreaded applications which use the Standard C++
@@ -1647,7 +1647,7 @@ A quick read of the relevant part of the GCC
</para>
<section xml:id="manual.intro.using.concurrency.prereq" xreflabel="Thread
Prereq"><info><title>Prerequisites</title></info>
-
+
<para>All normal disclaimers aside, multithreaded C++ application are
only supported when libstdc++ and all user code was built with
@@ -1686,7 +1686,7 @@ A quick read of the relevant part of the GCC
</section>
<section xml:id="manual.intro.using.concurrency.thread_safety"
xreflabel="Thread Safety"><info><title>Thread Safety</title></info>
-
+
<para>
In the terms of the 2011 C++ standard a thread-safe program is one which
@@ -1803,7 +1803,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
<code>begin</code>, <code>end</code>, <code>rbegin</code>,
<code>rend</code>,
<code>front</code>, <code>back</code>, <code>data</code>,
<code>find</code>, <code>lower_bound</code>, <code>upper_bound</code>,
- <code>equal_range</code>, <code>at</code>
+ <code>equal_range</code>, <code>at</code>
and, except in associative or unordered associative containers,
<code>operator[]</code>. In other words, although they are non-const
so that they can return mutable iterators, those member functions
@@ -1831,8 +1831,8 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
int i = *global_sp; // OK, operator* is const
int j = *local_sp; // OK, does not operate on global_sp
- // *global_sp = 2; // NOT OK, modifies int visible to other
threads
- // *local_sp = 2; // NOT OK, modifies int visible to other
threads
+ // *global_sp = 2; // NOT OK, modifies int visible to other
threads
+ // *local_sp = 2; // NOT OK, modifies int visible to other
threads
// global_sp.reset(); // NOT OK, reset is non-const
local_sp.reset(); // OK, does not operate on global_sp
@@ -1849,24 +1849,24 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
<para>For further details of the C++11 memory model see Hans-J. Boehm's
<link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://www.hboehm.info/c++mm/";>Threads
- and memory model for C++</link> pages, particularly the <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://www.hboehm.info/c++mm/threadsintro.html";>introduction</link>
+ and memory model for C++</link> pages, particularly the <link
xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://www.hboehm.info/c++mm/threadsintro.html";>introduction</link>
and <link xmlns:xlink="http://www.w3.org/1999/xlink";
xlink:href="https://www.hboehm.info/c++mm/user-faq.html";>FAQ</link>.
</para>
</section>
<section xml:id="manual.intro.using.concurrency.atomics"
xreflabel="Atomics"><info><title>Atomics</title></info>
-
+
<para>
</para>
</section>
<section xml:id="manual.intro.using.concurrency.io"
xreflabel="IO"><info><title>IO</title></info>
-
+
<para>This gets a bit tricky. Please read carefully, and bear with me.
</para>
<section xml:id="concurrency.io.structure"
xreflabel="Structure"><info><title>Structure</title></info>
-
+
<para>A wrapper
type called <code>__basic_file</code> provides our abstraction layer
for the <code>std::filebuf</code> classes. Nearly all decisions dealing
@@ -1880,7 +1880,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
</section>
<section xml:id="concurrency.io.defaults"
xreflabel="Defaults"><info><title>Defaults</title></info>
-
+
<para>The __basic_file type is simply a collection of small wrappers around
the C stdio layer (again, see the link under Structure). We do no
locking ourselves, but simply pass through to calls to
<code>fopen</code>,
@@ -1911,7 +1911,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
</section>
<section xml:id="concurrency.io.future"
xreflabel="Future"><info><title>Future</title></info>
-
+
<para> A
second choice may be available for I/O implementations: libio. This is
disabled by default, and in fact will not currently work due to other
@@ -1944,7 +1944,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
</section>
<section xml:id="concurrency.io.alt"
xreflabel="Alt"><info><title>Alternatives</title></info>
-
+
<para>Don't forget that other cstdio implementations are possible. You
could
easily write one to perform your own forms of locking, to solve your
"interesting" problems.
@@ -1954,7 +1954,7 @@ gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)
</section>
<section xml:id="manual.intro.using.concurrency.containers"
xreflabel="Containers"><info><title>Containers</title></info>
-
+
<para>This section discusses issues surrounding the design of
multithreaded applications which use Standard C++ containers.
diff --git a/libstdc++-v3/doc/xml/manual/using_exceptions.xml
b/libstdc++-v3/doc/xml/manual/using_exceptions.xml
index 485b269a59e..32bff85549f 100644
--- a/libstdc++-v3/doc/xml/manual/using_exceptions.xml
+++ b/libstdc++-v3/doc/xml/manual/using_exceptions.xml
@@ -1,4 +1,4 @@
-<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<section xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="manual.intro.using.exceptions" xreflabel="Using Exceptions">
<?dbhtml filename="using_exceptions.html"?>
@@ -451,7 +451,7 @@ is called.
Error and Exception Handling
</link>
</title>
-
+
<author><personname><firstname>David</firstname><surname>Abrahams
</surname></personname></author>
<publisher>
<publishername>
@@ -468,7 +468,7 @@ is called.
Exception-Safety in Generic Components
</link>
</title>
-
+
<author><personname><firstname>David</firstname><surname>Abrahams</surname></personname></author>
<publisher>
<publishername>
diff --git a/libstdc++-v3/doc/xml/manual/utilities.xml
b/libstdc++-v3/doc/xml/manual/utilities.xml
index 469d85f4109..e155c8c3943 100644
--- a/libstdc++-v3/doc/xml/manual/utilities.xml
+++ b/libstdc++-v3/doc/xml/manual/utilities.xml
@@ -1,4 +1,4 @@
-<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
+<chapter xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="std.util" xreflabel="Utilities">
<?dbhtml filename="utilities.html"?>
@@ -17,7 +17,7 @@
<!-- Section 01 : Functors -->
<section xml:id="std.util.functors"
xreflabel="Functors"><info><title>Functors</title></info>
<?dbhtml filename="functors.html"?>
-
+
<para>If you don't know what functors are, you're not alone. Many people
get slightly the wrong idea. In the interest of not reinventing
the wheel, we will refer you to the introduction to the functor
@@ -30,7 +30,7 @@
<!-- Section 02 : Pairs -->
<section xml:id="std.util.pairs"
xreflabel="Pairs"><info><title>Pairs</title></info>
<?dbhtml filename="pairs.html"?>
-
+
<para>The <code>pair<T1,T2></code> is a simple and handy way to
carry around a pair of objects. One is of type T1, and another of
type T2; they may be the same type, but you don't get anything
@@ -85,7 +85,7 @@
<!-- Section 03 : Memory -->
<section xml:id="std.util.memory"
xreflabel="Memory"><info><title>Memory</title></info>
<?dbhtml filename="memory.html"?>
-
+
<para>
Memory contains three general areas. First, function and operator
calls via <function>new</function> and <function>delete</function>
@@ -111,7 +111,7 @@
<!-- Section 04 : Traits -->
<section xml:id="std.util.traits"
xreflabel="Traits"><info><title>Traits</title></info>
<?dbhtml filename="traits.html"?>
-
+
<para>
</para>
</section>
