gcc-wwwdocs branch master updated. d0940daacb227ce9f2dcfe64c56c4bd64b899750

gcc-wwwdocs branch master updated. d0940daacb227ce9f2dcfe64c56c4bd64b899750

[Gerald Pfeifer]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  d0940daacb227ce9f2dcfe64c56c4bd64b899750 (commit)
      from  002304c326220927b1b7071818988d1325badd9b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d0940daacb227ce9f2dcfe64c56c4bd64b899750
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri Oct 21 07:54:54 2022 +0200

    *: Standardize on <hr> over <hr />
    
    We have largely been using <hr /> as the canonical form as opposed to
    <hr>. HTML 5 actively recommends against that, so standardize on <hr>.

diff --git a/htdocs/about.html b/htdocs/about.html
index faf1252e..7278cae6 100644
--- a/htdocs/about.html
+++ b/htdocs/about.html
@@ -48,7 +48,7 @@ a higher chance of being implemented soon. ;-)</p>
 </ul>
 
 
-<hr />
+<hr>
 <h2 id="git">Using the git repository</h2>
 
 <p>Assuming you have both git 
diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index c6e01827..d3a50f2a 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -37,7 +37,7 @@
 </li>
 </ul>
 
-<hr />
+<hr>
 
 <h1 id="report">Reporting Bugs</h1>
 
@@ -245,7 +245,7 @@ use it.</p>
 header.  It is likely to be very large and we can't use it to
 reproduce the problem.</p>
 
-<hr />
+<hr>
 
 <h1 id="known">Frequently Reported Bugs</h1>
 
@@ -255,7 +255,7 @@ Often, reports get a low priority when there is a simple work-around.
 In particular, bugs caused by invalid code have a simple work-around:
 <em>fix the code</em>.</p>
 
-<hr />
+<hr>
 
 <h1 id="nonbugs">Non-bugs</h1>
 
@@ -270,7 +270,7 @@ invalid that used to be conforming (this holds especially for C++).
 In either case, you should update your code to match recent language
 standards.</p>
 
-<hr />
+<hr>
 
 <h2 id="nonbugs_general">General</h2>
 
@@ -304,7 +304,7 @@ Every Computer Scientist Should Know about Floating-Point Arithmetic</a>
 for more information.</p></dd>
 </dl>
 
-<hr />
+<hr>
 
 <h2 id="nonbugs_c">C</h2>
 
@@ -530,7 +530,7 @@ for details.
 </p></dd>
 </dl>
 
-<hr />
+<hr>
 
 <h2 id="nonbugs_cxx">C++</h2>
 
diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index 5963d985..342c12a8 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -30,7 +30,7 @@ contributions must meet:</p>
 <li><a href="#announce">Announcing Changes (to our Users)</a></li>
 </ul>
 
-<hr />
+<hr>
 
 <h2 id="legal">Legal Prerequisites</h2>
 
diff --git a/htdocs/egcs-1.1/egcs-1.1-branch.html b/htdocs/egcs-1.1/egcs-1.1-branch.html
index 34c91688..7e0858c6 100644
--- a/htdocs/egcs-1.1/egcs-1.1-branch.html
+++ b/htdocs/egcs-1.1/egcs-1.1-branch.html
@@ -30,7 +30,7 @@ option #2 or #3 is recommended.</p>
 <p>FTP snapshots will track the EGCS 1.1 release only.  After EGCS 1.1 is
 released, snapshots will return to tracking the mainline sources.</p>
 
-<hr />
+<hr>
 <p>All patches for the EGCS 1.1 release branch must be approved by either
 someone with global write privs or that maintains the specific file being
 patched.  At some point in the near future, all patches will need to go through
diff --git a/htdocs/egcs-1.1/regress.html b/htdocs/egcs-1.1/regress.html
index 5ab6fe7c..0a9f1a80 100644
--- a/htdocs/egcs-1.1/regress.html
+++ b/htdocs/egcs-1.1/regress.html
@@ -65,7 +65,7 @@ those files to the testing coordinator law@cygnus.com.</p>
 <p>Note that you will receive many failures from GCC 2.8.1 and EGCS 1.0.3a when
 running the gcc testsuites because those versions of the compiler do not
 support -Os.</p>
-<hr />
+<hr>
 
 <h2>Current Regression Testing Status</h2>
 
diff --git a/htdocs/faq.html b/htdocs/faq.html
index 69e938e5..183e7bec 100644
--- a/htdocs/faq.html
+++ b/htdocs/faq.html
@@ -21,7 +21,7 @@ the <a href="http://c-faq.com/">comp.lang.c FAQ</a> and the
    <a href="https://gcc.gnu.org/onlinedocs/libstdc++/faq.html">
     libstdc++-v3</a>.</p>
 
-<hr />
+<hr>
 <h1>Questions</h1>
 <ol>
   <li><a href="#general">General information</a>
@@ -57,7 +57,7 @@ the <a href="http://c-faq.com/">comp.lang.c FAQ</a> and the
 </ol>
 
 
-<hr />
+<hr>
 <h1 id="general">General information</h1>
 
 <h2 id="support">How do I get a bug fixed or a feature added?</h2>
@@ -91,7 +91,7 @@ disadvantages.</p>
     money, but is relatively likely to get results.</li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="platforms">Does GCC work on my platform?</h2>
 
 <p>The host/target specific installation notes for GCC include information
@@ -102,7 +102,7 @@ is always available at the GCC web site.
 Reports of <a href="buildstat.html">successful builds</a>
 for several versions of GCC are also available at the web site.</p>
 
-<hr />
+<hr>
 <h1 id="installation">Installation</h1>
 
 <h2 id="multiple">How to install multiple versions of GCC</h2>
@@ -164,7 +164,7 @@ configure --program-suffix=-2.95.2 &lt;other configure options&gt;
 <code>/usr/local/bin/gcc-2.95.2</code> instead of
 <code>/usr/local/bin/gcc</code>.</p>
 
-<hr />
+<hr>
 <h2 id="rpath">Dynamic linker is unable to find GCC libraries</h2>
 
 <p>This problem manifests itself by programs not finding shared
@@ -200,7 +200,7 @@ or ld that adds the appropriate directory to the environment variable
 platform-dependent).</p>
 
 
-<hr />
+<hr>
 <h2 id="gas">GCC can not find GNU as/GNU ld</h2>
 <p>GCC searches the PATH for an assembler and a linker, but it only
 does so after searching a directory list hard-coded in the GCC
@@ -237,7 +237,7 @@ is that it won't allow you to override the search path for assembler
 and linker with command-line options <code>-B/path/</code> if the
 specified filenames exist.</p>
 
-<hr />
+<hr>
 <h2 id="environ">cpp: Usage:... Error</h2>
 
 <p>If you get an error like this when building GCC (particularly when building
@@ -254,7 +254,7 @@ or end of these variables is an implicit '.' and will cause problems.</p>
 <p>Also note '::' in these paths will also cause similar problems.</p>
 
 
-<hr />
+<hr>
 <h1 id="testsuite">Testsuite problems</h1>
 
 <h2 id="testoptions">How do I pass flags like <code>-fnew-abi</code> to
@@ -271,7 +271,7 @@ the testsuite?</h2>
   make RUNTESTFLAGS="--tool_opts '-fnew-abi -fno-honor-std'" check-g++
 </pre>
 
-<hr />
+<hr>
 <h2 id="multipletests"> How can I run the testsuite with multiple options? </h2>
 
 <p>If you invoke <code>runtest</code> directly, you can use the
@@ -291,7 +291,7 @@ no additional flags.</p>
 <p>This technique is particularly useful on multilibbed targets.</p>
 
 
-<hr />
+<hr>
 <h1 id="misc">Miscellaneous</h1>
 
 
@@ -349,7 +349,7 @@ that the forward declaration was not necessary, but, according to the
 final version of the Standard, it is.</p>
 
 
-<hr />
+<hr>
 <h2 id="dso"><code>dynamic_cast</code>, <code>throw</code>, <code>typeid</code> don't work with shared libraries</h2>
 
 <p>The new C++ ABI in the GCC 3.0 series uses address comparisons,
@@ -408,7 +408,7 @@ resolved all begin with "_ZTS". Refer to <code>ld</code>'s
 documentation for a description of the "<code>-E</code>" &amp;
 "<code>-Bsymbolic</code>" flags.</p>
 
-<hr />
+<hr>
 <h2 id="generated_files">Why do I need autoconf, bison, xgettext, automake, etc?</h2>
 
 <p>If you're using diffs up dated from one snapshot to the next, or
@@ -431,7 +431,7 @@ need <a href="https://gcc.gnu.org/install/prerequisites.html#TOC1">some
 additional tools</a>.</p>
 
 
-<hr />
+<hr>
 <h2 id="picflag-needed">Why can't I build a shared library?</h2>
 
 <p>When building a shared library you may get an error message from the
@@ -455,7 +455,7 @@ support PIC in this manner.  For example:</p>
 </pre>
 
 
-<hr />
+<hr>
 <h2 id="vtables">When building C++, the linker says my constructors, destructors or virtual tables are undefined, but I defined them</h2>
 
 <p>The ISO C++ Standard specifies that all virtual methods of a class
diff --git a/htdocs/gcc-2.95/branch.html b/htdocs/gcc-2.95/branch.html
index 1f92ed1b..7336d09c 100644
--- a/htdocs/gcc-2.95/branch.html
+++ b/htdocs/gcc-2.95/branch.html
@@ -32,7 +32,7 @@ release, option #2 or #3 is recommended.</p>
 <p>Snapshots will track the GCC 2.95 release only.  After GCC 2.95 is
 released, snapshots will return to tracking the mainline sources.</p>
 
-<hr />
+<hr>
 <p>All patches for the GCC 2.95 release branch must be approved by the
 release coordinator (Jeff Law).</p>
 
diff --git a/htdocs/gcc-3.0/index.html b/htdocs/gcc-3.0/index.html
index 864d01d1..a1f454e0 100644
--- a/htdocs/gcc-3.0/index.html
+++ b/htdocs/gcc-3.0/index.html
@@ -48,7 +48,7 @@ group of volunteers</a> is what makes GCC successful.</p>
 <p>To obtain GCC please use <a href="../mirrors.html">our mirror sites</a>,
 or our CVS server.</p>
 
-<hr />
+<hr>
 
 <h2>Previous 3.0.x Releases</h2>
 
diff --git a/htdocs/gcc-3.1/index.html b/htdocs/gcc-3.1/index.html
index e97d0dcc..0c85bcb9 100644
--- a/htdocs/gcc-3.1/index.html
+++ b/htdocs/gcc-3.1/index.html
@@ -46,7 +46,7 @@ group of volunteers</a> is what makes GCC successful.</p>
 <p>To obtain GCC please use <a href="../mirrors.html">our mirror sites</a>,
 or our CVS server.</p>
 
-<hr />
+<hr>
 
 </body>
 </html>
diff --git a/htdocs/gcc-3.2/changes.html b/htdocs/gcc-3.2/changes.html
index 0faf69ea..7b9ea63f 100644
--- a/htdocs/gcc-3.2/changes.html
+++ b/htdocs/gcc-3.2/changes.html
@@ -96,7 +96,7 @@
 
 <!-- Changes for later point releases should be added at the top. -->
 
-<hr />
+<hr>
 <h2 id="GCC3.2.3">GCC 3.2.3</h2>
 
 <p>3.2.3 is a bug fix release only; there are no new features that
@@ -227,7 +227,7 @@ changed to make them more clear.</p>
 <li><a href="https://gcc.gnu.org/PR6955">6955</a>: collect2 says "core dumped" when there is no core</li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.2.2">GCC 3.2.2</h2>
 
 <p>Beginning with 3.2.2, GCC's Makefile suite supports redirection of
@@ -362,7 +362,7 @@ changed to make them more clear.</p>
 <li><a href="https://gcc.gnu.org/PR7448">7448</a>, <a href="https://gcc.gnu.org/PR8882">8882</a>: typo cleanups</li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.2.1">GCC 3.2.1</h2>
 
 <p>3.2.1 adds a new warning, <code>-Wabi</code>. This option warns when GNU
@@ -554,7 +554,7 @@ GCC 3.2.1.</p>
 <li><a href="https://gcc.gnu.org/PR8120">8120</a>: Update documentation of bad use of <code>##</code></li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.2">GCC 3.2</h2>
 
 <p>3.2 is a small bug fix release, but there is a change to the application
diff --git a/htdocs/gcc-3.3/changes.html b/htdocs/gcc-3.3/changes.html
index 4cb07f07..93d96e65 100644
--- a/htdocs/gcc-3.3/changes.html
+++ b/htdocs/gcc-3.3/changes.html
@@ -435,7 +435,7 @@
     <code>DESTDIR</code>.</li>
   </ul>
 
-<hr />
+<hr>
 <h2>GCC 3.3</h2>
 <p>
 Detailed release notes for the GCC 3.3 release follow.
@@ -705,7 +705,7 @@ Detailed release notes for the GCC 3.3 release follow.
 <li><a href="https://gcc.gnu.org/PR10308">10308</a> [x86] ICE with <code>-O -fgcse</code> or <code>-O2</code></li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.3.1">GCC 3.3.1</h2>
 
 <h3>Bug Fixes</h3>
@@ -914,7 +914,7 @@ here).</p>
 <li><a href="https://gcc.gnu.org/PR10810">10810</a> gcc-3.3 fails make check: buffer overrun in <code>test_demangle.c</code></li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.3.2">GCC 3.3.2</h2>
 
 <h3>Bug Fixes</h3>
@@ -1045,7 +1045,7 @@ not listed here).</p>
 <li><a href="https://gcc.gnu.org/PR11903">11903</a> [sh4] <code>-pthread</code> fails to link due to error in spec file on sh4</li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.3.3">GCC 3.3.3</h2>
 
 <h3>Minor features</h3>
@@ -1274,7 +1274,7 @@ the relevant defect report.</p>
 </ul>
 
 
-<hr />
+<hr>
 <h2 id="GCC3.3.4">GCC 3.3.4</h2>
 
 <p>This is the <a
@@ -1285,7 +1285,7 @@ complete (that is, it is possible that some PRs that have been fixed
 are not listed here).</p>
 
 
-<hr />
+<hr>
 <h2 id="GCC3.3.5">GCC 3.3.5</h2>
 
 <p>This is the <a
@@ -1296,7 +1296,7 @@ complete (that is, it is possible that some PRs that have been fixed
 are not listed here).</p>
 
 
-<hr />
+<hr>
 <h2 id="GCC3.3.6">GCC 3.3.6</h2>
 
 <p>This is the <a
diff --git a/htdocs/gcc-3.4/changes.html b/htdocs/gcc-3.4/changes.html
index 451245aa..aac9a245 100644
--- a/htdocs/gcc-3.4/changes.html
+++ b/htdocs/gcc-3.4/changes.html
@@ -1218,7 +1218,7 @@ and not your code, that is broken.</em></p>
         for non-optimizing compilations.</li>
   </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.4.0">GCC 3.4.0</h2>
 
 <h3>Bug Fixes</h3>
@@ -1232,7 +1232,7 @@ this link</a> to query the Bugzilla database for the list of over 900 bugs
 fixed in 3.4.0.  This is the list of all bugs marked as resolved and fixed
 in 3.4.0 that are not flagged as 3.4 regressions.</p>
 
-<hr />
+<hr>
 <h2 id="GCC3.4.1">GCC 3.4.1</h2>
 
 
@@ -1456,7 +1456,7 @@ here).</p>
 <li><a href="https://gcc.gnu.org/PR15123">15123</a> libstdc++<code>-doc</code>: Allocators.3 manpage is empty</li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.4.2">GCC 3.4.2</h2>
 
 
@@ -1607,7 +1607,7 @@ here).</p>
 <li><a href="https://gcc.gnu.org/PR16250">16250</a> ada/doctools runs makeinfo even in release tarball</li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="GCC3.4.3">GCC 3.4.3</h2>
 
 <p>This is the <a
@@ -1731,7 +1731,7 @@ are not listed here).</p>
 <li><a href="https://gcc.gnu.org/PR16406">16406</a> USE_LD_AS_NEEDED undocumented</li>
 </ul>
 
-<hr />
+<hr>
 
 <h2 id="GCC3.4.4">GCC 3.4.4</h2>
 
@@ -1742,7 +1742,7 @@ known to be fixed in the 3.4.4 release. This list might not be
 complete (that is, it is possible that some PRs that have been fixed
 are not listed here).</p>
 
-<hr />
+<hr>
 
 <h2 id="GCC3.4.5">GCC 3.4.5</h2>
 
@@ -2002,7 +2002,7 @@ comparison failure</li>
 <code>-fpeephole2</code></li>
 </ul>
 
-<hr />
+<hr>
 
 <h2 id="GCC3.4.6">GCC 3.4.6</h2>
 
diff --git a/htdocs/gcc-4.0/changes.html b/htdocs/gcc-4.0/changes.html
index d5957957..cd5751dd 100644
--- a/htdocs/gcc-4.0/changes.html
+++ b/htdocs/gcc-4.0/changes.html
@@ -594,7 +594,7 @@ class N::A {
 	https://gcc.gnu.org/wiki/Visibility</a>.</li>
   </ul>
 
-<hr />
+<hr>
 <h2 id="GCC4.0.1">GCC 4.0.1</h2>
 
 <p>This is the <a
diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 18d2f0c6..e4dadb27 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -15,7 +15,7 @@ maintainers and significant developers.</p>
 
 <p>Our <a href="about.html#git">web pages are managed via git</a>.</p>
 
-<hr />
+<hr>
 <h2>Contents</h2>
 <ol>
   <li><a href="#authenticated">Authenticated access</a></li>
@@ -28,7 +28,7 @@ maintainers and significant developers.</p>
   <li><a href="#account">Tips&amp;Tricks around your account</a></li>
 </ol>
 
-<hr />
+<hr>
 <h2 id="authenticated">Authenticated access</h2>
 
 <p>We provide authenticated access via the SSH protocol.  This needs to
@@ -57,7 +57,7 @@ test write access (approval from the mailing list is not needed in this
 one case).  For all other changes, please be sure to follow the write
 access policies below.</p>
 
-<hr />
+<hr>
 <h2 id="setup">Setting up your local Git tree</h2>
 
 <p>Check out the GCC sources by issuing the command:</p>
@@ -100,7 +100,7 @@ commits from that in <samp>$HOME/.gitconfig</samp>, you can configure
 that in an individual Git tree using similar invocations
 without <code>--global</code>.</p>
 
-<hr />
+<hr>
 <h2 id="policies">Write access policies</h2>
 
 <p>The GCC project grants developers various levels of write access to
@@ -177,7 +177,7 @@ certification.  Merging such developments back to the mainline still needs
 approval in the usual way.</p>
 
 
-<hr />
+<hr>
 <h2 id="testing">Testing changes</h2>
 
 <p>All changes must be tested according to the 
@@ -206,7 +206,7 @@ minimize the amount of time where the tree does not build at
 all. Repeated failure to adhere to these rules could result in the
 revocation of check-in privileges by the Steering Committee.</p>
 
-<hr />
+<hr>
 <h2 id="checkin">Checking in a change</h2>
 
 <p>The following is meant to provide a very quick overview of how to
@@ -289,7 +289,7 @@ hint: See the 'Note about fast-forwards' in 'git push --help' for details.
 </li>
 </ol>
 
-<hr />
+<hr>
 <h2 id="branches">Creating and using branches</h2>
 
 <p>Git makes it very easy and cheap to create local branches for working on
@@ -323,7 +323,7 @@ git push origin $BRANCH:devel/$BRANCH
 hand occasionally as needed with a normal <code>git merge master</code>.  But
 DO NOT then simply merge the branch back onto master; see below.</p>
 
-<hr />
+<hr>
 <h2 id="merges">Merging and Rebasing</h2>
 
 <p>Every commit in the history of GCC master must follow the testing guidelines
@@ -345,7 +345,7 @@ accordingly.  It may be easier to cherry-pick some smaller changes onto master
 don't need to <code>merge --squash</code> squash, but still need to make sure
 the commits on the branch satisfy the above rules for commits.
 
-<hr />
+<hr>
 <h2 id="vendor">Personal and vendor branches</h2>
 
 The GCC git repository is used by many people and the branch and tag
@@ -524,7 +524,7 @@ check the branch out locally.  You can do that afterwards with
     git push users/me me/topic
 </pre></blockquote>
 
-<hr />
+<hr>
 <h2 id="account">Tips&amp;Tricks around your account</h2>
 
 <p>Your gcc.gnu.org account also receives e-mail (and is what you
diff --git a/htdocs/index.html b/htdocs/index.html
index 51f9c95c..39060016 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -40,7 +40,7 @@ steering committee</a>, guided by the <a href="gccmission.html">
 mission statement</a>.</p>
 
 
-<hr />
+<hr>
 <!-- ==================================================================== -->
 
 
diff --git a/htdocs/lists.html b/htdocs/lists.html
index 65bf78c5..b50e9ac3 100644
--- a/htdocs/lists.html
+++ b/htdocs/lists.html
@@ -285,7 +285,7 @@ e-mail addresses.</p>
 <p>See also <a href="spam.html">information about dealing with spam on
 the lists</a>.</p>
 
-<hr />
+<hr>
 
 <p id="searchbox">Search the contents gcc.gnu.org:</p>
 
diff --git a/htdocs/news/profiledriven.html b/htdocs/news/profiledriven.html
index 4b4d58f8..13a61ec0 100644
--- a/htdocs/news/profiledriven.html
+++ b/htdocs/news/profiledriven.html
@@ -257,7 +257,7 @@ releases.  For more information about these testers, check <a
 href="../benchmarks/">our benchmarks page</a>.
 </p>
 
-<hr />
+<hr>
 
 <h3>References</h3>
 
diff --git a/htdocs/projects/documentation.html b/htdocs/projects/documentation.html
index e369accc..00d9217b 100644
--- a/htdocs/projects/documentation.html
+++ b/htdocs/projects/documentation.html
@@ -47,7 +47,7 @@ without including all relevant documentation changes.</p>
 familiar with what is documented where, and what documentation appears
 to be missing.  Report or fix any problems you see.</p>
 
-<hr />
+<hr>
 
 <h2 id="frontend_middleend_interface">Fully document the interface of front ends to GCC</h2>
 
diff --git a/htdocs/projects/index.html b/htdocs/projects/index.html
index b095b1a8..c9887773 100644
--- a/htdocs/projects/index.html
+++ b/htdocs/projects/index.html
@@ -40,7 +40,7 @@ help develop GCC:</p>
 <p>Remember to <a href="../contributewhy.html">keep other developers
 informed</a> of any substantial projects you intend to work on.</p>
 
-<hr />
+<hr>
 
 <h2 id="improve_the_installation_procedure">Improve the installation procedure</h2>
 
diff --git a/htdocs/projects/optimize.html b/htdocs/projects/optimize.html
index 8fc3b4cf..26262637 100644
--- a/htdocs/projects/optimize.html
+++ b/htdocs/projects/optimize.html
@@ -38,7 +38,7 @@ turn it back on.)</p>
 </ul>
 <!-- table of contents end -->
 
-<hr />
+<hr>
 <h2 id="putting_constants_in_special_sections">Putting constants in special sections.</h2>
 
 <p>If a function has been placed in a special
@@ -47,7 +47,7 @@ constants in a special section too.  But which one?  (Being able to
 specify a section for string constants would be useful for the Linux
 kernel.)</p>
 
-<hr />
+<hr>
 <h2 id="un_cse">Un-cse.</h2>
 
 <p>Perhaps we should have an un-cse step right after cse, which tries to
@@ -56,7 +56,7 @@ reg everywhere, if that looks like an improvement.  Which is if the
 reg is used only a few times.  Use rtx_cost to determine if the
 change is really an improvement.</p>
 
-<hr />
+<hr>
 <h2 id="clean_up_how_cse_works">Clean up how cse works.</h2>
 
 <p>The scheme is that each value has just one hash entry.  The
@@ -111,7 +111,7 @@ the lists of which regs or mems hold a particular value.  It is easy
 to see if there is a reg or mem that is equiv to a particular value.
 If the value is constant, it is always explicitly constant.</p>
 
-<hr />
+<hr>
 <h2 id="loop_optimization">Loop optimization</h2>
 
 <p>Strength reduction and iteration variable elimination could be
@@ -125,7 +125,7 @@ another in its place.</p>
 variable will be at the end of the loop, and eliminate the variable
 within the loop by computing that value at the loop end.</p>
 
-<hr />
+<hr>
 <h2 id="using_constraints_on_values">Using constraints on values</h2>
 
 <p>Many operations could be simplified based on knowledge of the
@@ -143,7 +143,7 @@ operations are redundant.  Constraints might permit a decrement and
 branch instruction that checks zeroness to be used when the user has
 specified to exit if negative.</p>
 
-<hr />
+<hr>
 <h2 id="change_the_type_of_a_variable">Change the type of a variable</h2>
 
 <p>Sometimes a variable is declared as <code>int</code>, it is
@@ -153,20 +153,20 @@ better code would result if the variable had type <code>char</code>.
 If the compiler could detect this case, it could change the
 declaration of the variable and change all the places that use it.</p>
 
-<hr />
+<hr>
 <h2 id="better_handling_for_very_sparse_switches">Better handling for very sparse switches</h2>
 
 <p>There may be cases where it would be better to compile a switch
 statement to use a fixed hash table rather than the current
 combination of jump tables and binary search.</p>
 
-<hr />
+<hr>
 <h2 id="order_of_subexpressions">Order of subexpressions</h2>
 
 <p>It might be possible to make better code by paying attention to the
 order in which to generate code for subexpressions of an expression.</p>
 
-<hr />
+<hr>
 <h2 id="distributive_law">Distributive law</h2>
 
 <p>The C expression <code>*(X + 4 * (Y + C))</code> compiles better on
@@ -176,7 +176,7 @@ for which machines, to use each alternative.</p>
 
 <p>Some work has been done on this, in combine.c.</p>
 
-<hr />
+<hr>
 <h2 id="better_builtin_string_functions">Better builtin string functions</h2>
 
 <p>Although GCC implements numerous optimizations of the standard C
@@ -250,7 +250,7 @@ internal functions in the expansion of the macro.</p>
 <code>-Os</code> is specified.</p>
 
 
-<hr />
+<hr>
 <h2 id="data_prefetch">Data prefetch support</h2>
 
 <p>Loads from memory can take many cycles if the loaded data is not in
@@ -265,7 +265,7 @@ page describes
 <a href="prefetch.html">data prefetch support and optimizations</a> that
 are in development or already supported by GCC.</p>
 
-<hr />
+<hr>
 <h2 id="target-specific">Target specific optimizer deficiencies</h2>
 
 <p>Almost all code transformations implemented in GCC are target
diff --git a/htdocs/projects/tree-ssa/index.html b/htdocs/projects/tree-ssa/index.html
index 7d3740e4..21f5885e 100644
--- a/htdocs/projects/tree-ssa/index.html
+++ b/htdocs/projects/tree-ssa/index.html
@@ -26,7 +26,7 @@
 <li><a href="#todo">TODO list (last updated: 2003-12-27)</a></li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="news">Latest News</h2>
 
 <dl>
@@ -56,7 +56,7 @@ href="https://gcc.gnu.org/ml/gcc/2004-03/msg00596.html">https://gcc.gnu.org/ml/g
     April.</p></dd>
 </dl>
 
-<hr />
+<hr>
 <h3 id="intro">Introduction</h3>
 
 <p>The goal of this project is to build an optimization framework for trees
@@ -64,7 +64,7 @@ based on the Static Single Assignment (SSA) form [<a
 href="#cytron.ea-91">1</a>].  The implementation currently lives in the
 <code>tree-ssa-20020619-branch</code> branch.</p>
 
-<hr />
+<hr>
 <h3 id="documentation">Documentation</h3>
 
 <p>A high-level overview of GENERIC/GIMPLE and the SSA implementation may
@@ -77,7 +77,7 @@ documentation (<code>doc/gccint.info</code> in GCC's build directory).</p>
 <p>Many further bits of information also can be found in the <a
 href="https://gcc.gnu.org/wiki/GettingStarted">GCC Wiki</a>.</p>
 
-<hr />
+<hr>
 <h3 id="contributing">Contributing</h3>
 
 <p>Checkout the <code>tree-ssa-20020619-branch</code> branch
@@ -100,7 +100,7 @@ Elliston, Andrew Haley, Richard Henderson, Graydon Hoare, Jan Hubicka, Aldy
 Hernandez, Andreas Jaeger, Jeff Law, Andrew MacLeod, Toon Moene, Jason Merrill,
 Diego Novillo, Sebastian Pop, Graham Stott and Jeff Sturm.</p>
 
-<hr />
+<hr>
 <h3 id="stability">Branch stability</h3>
 
 <p>Every patch submitted for review must either fix a PR or adress one
@@ -117,7 +117,7 @@ latest merge tag is always added to GCC's version string.  A merge may
 be postponed if there is major breakage in mainline.</p>
 
 
-<hr />
+<hr>
 <h2 id="gimple">GENERIC and GIMPLE</h2>
 
 <p>While GCC trees contain sufficient information for
@@ -182,7 +182,7 @@ functions in <code>c-simplify.c</code>, the C++ front end has its own in
 <code>cp/cp-simplify.c</code>.  Predicates to determine whether a tree is
 in GIMPLE form are defined in <code>tree-simple.[ch]</code>.</p>
 
-<hr />
+<hr>
 <h2 id="ssa">SSA implementation</h2>
 
 <p>Having trees in GIMPLE form enables language-independent analysis
@@ -213,7 +213,7 @@ code.</li>
 <li>Rewrite the tree in SSA form.  Implemented in <code>tree-ssa.c</code>.</li>
 </ol>
 
-<hr />
+<hr>
 <h2 id="unparse">Unparsing C trees</h2>
 
 <p>The file <code>tree-pretty-print.c</code> implements several debugging
@@ -221,12 +221,12 @@ functions that given a GENERIC tree node, they print a C representation of
 the tree.  The output is not meant to be compilable, but it is of great
 help when debugging transformations done by the transformation passes.</p>
 
-<hr />
+<hr>
 <h2 id="tb">Tree Browser</h2>
 For debugging, browsing, discovering, and playing with trees you can
 use the <a href="tree-browser.html">Tree Browser</a> directly from gdb.
 
-<hr />
+<hr>
 <h2 id="status">Implementation Status</h2>
 
 <p>This is a short list of the work that has already been finished or
@@ -277,7 +277,7 @@ framework have the ability to dump an annotated intermediate representation.
 Support for scanning these tree dumps has been implemented for the
 existing DejaGNU testing framework.</p>
 
-<hr />
+<hr>
 <h2 id="todo">TODO list</h2>
 
 <p>This is a loosely organized list of unimplemented features,
@@ -358,7 +358,7 @@ different passes are welcome.</p>
 </dl>
 
 
-<hr />
+<hr>
 <h2>References</h2>
 
 <dl>
diff --git a/htdocs/projects/tree-ssa/tree-browser.html b/htdocs/projects/tree-ssa/tree-browser.html
index 1dd84295..23f46e92 100644
--- a/htdocs/projects/tree-ssa/tree-browser.html
+++ b/htdocs/projects/tree-ssa/tree-browser.html
@@ -12,7 +12,7 @@
     <!-- banner -->
    <p class="bold"><br>Tree Browser has been removed from GCC,
    and this page is no longer up-to-date.<br><br></p>
-    <hr />
+    <hr>
 
 <h1>Tree Browser</h1>
     
diff --git a/htdocs/projects/x86.html b/htdocs/projects/x86.html
index 7c94c062..3ce49e7e 100644
--- a/htdocs/projects/x86.html
+++ b/htdocs/projects/x86.html
@@ -32,7 +32,7 @@ turn it back on.)</p>
 <li><a href="#pathetic-loop">More pathetic failures of loop optimization</a></li>
 </ul>
 
-<hr />
+<hr>
 <h2 id="csefail">Failure of common subexpression elimination</h2>
 
 <p>(12 Nov 2004, reconfirmed with trunk revision 156706) Common
@@ -116,7 +116,7 @@ However, we know that can't happen here, because <code>(reg:QI
 <code>zero_extend</code>.  If it were negative, we would have jumped
 to <code>.L2</code>.</p>
 
-<hr />
+<hr>
 <h2 id="storemerge">Store merging</h2>
 
 <p>(12 Nov 2004, reconfirmed with trunk revision 156706) GCC
@@ -193,7 +193,7 @@ a more general function where the values assigned to
 <code>'code'</code> and <code>'mode'</code> were not constant, but the
 advantage is less obvious here.</p>
 
-<hr />
+<hr>
 <h2 id="volatile">Volatile inhibits too many optimizations</h2>
 
 <p>(12 Nov 2004, reconfirmed with trunk revision 156706) GCC refuses
@@ -233,7 +233,7 @@ functions above have identical semantics.  On other platforms that
 have in-memory operations, that may not be the case, and the C
 standard may take issue with the difference - we aren't sure.</p>
 
-<hr />
+<hr>
 <h2 id="rndmode">Unnecessary changes of rounding mode</h2>
 
 <p>(12 Nov 2004, reconfirmed with trunk revision 156706) GCC does not
@@ -340,7 +340,7 @@ d2i2:
 	ret
 </pre>
 
-<hr />
+<hr>
 <h2 id="fpmove">Moving floating point through integer registers</h2>
 
 <p>(22 Jan 2000, reconfirmed with trunk revision 156706) GCC knows how
@@ -478,7 +478,7 @@ two blocks of four megabytes each, averaged over a hundred runs.</p>
 <tr><td>fcpy3</td>   <td></td>         <td></td>           <td>2.860</td> <td>72.37</td></tr>
 </table>
 
-<hr />
+<hr>
 <h2 id="pathetic-loop">More pathetic failures of loop optimization</h2>
 
 <p>(25 Aug 2001) Consider the following code, which is a trimmed down
diff --git a/htdocs/search.html b/htdocs/search.html
index 2f006551..83f26fb5 100644
--- a/htdocs/search.html
+++ b/htdocs/search.html
@@ -9,7 +9,7 @@
 
 <body>
 <h1><a href="index.html">GCC</a> detailed search</h1>
-<hr />
+<hr>
 <form method="get" action="https://gcc.gnu.org/cgi-bin/htsearch">
 Match: <select name="method">
 <option value="boolean">Boolean expression</option>
@@ -38,7 +38,7 @@ Sort by: <select name="sort">
 <input type="submit" value="Search:" />
 <input type="text" size="50" name="words" value="" />
 <br>
-<hr />
+<hr>
 <!-- Synopsis: Optionally restrict the search.  One fairly general
      select-menu and detailed choices for each different web-area.
      For the mailing lists, may select by list or by specific month for a
@@ -2237,7 +2237,7 @@ Mailing lists, including those for the old egcs project.  Ticking a box is like
 
 <p> <input type="reset" /> </p>
 </form>
-<hr />
+<hr>
 
 <p id="syntax">
 In a <em>boolean expression</em>, the words searched for, or parts inside
@@ -2252,7 +2252,7 @@ parentheses <b>()</b> are separated by the operator-words <b>and</b>,
 </ul>
 Note that the operator <b>not</b> is binary, having the meaning of
 'without'.
-<hr />
+<hr>
 
 <em>Database last updated</em>
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/about.html                          |  2 +-
 htdocs/bugs/index.html                     | 12 ++++++------
 htdocs/contribute.html                     |  2 +-
 htdocs/egcs-1.1/egcs-1.1-branch.html       |  2 +-
 htdocs/egcs-1.1/regress.html               |  2 +-
 htdocs/faq.html                            | 28 ++++++++++++++--------------
 htdocs/gcc-2.95/branch.html                |  2 +-
 htdocs/gcc-3.0/index.html                  |  2 +-
 htdocs/gcc-3.1/index.html                  |  2 +-
 htdocs/gcc-3.2/changes.html                |  8 ++++----
 htdocs/gcc-3.3/changes.html                | 14 +++++++-------
 htdocs/gcc-3.4/changes.html                | 14 +++++++-------
 htdocs/gcc-4.0/changes.html                |  2 +-
 htdocs/gitwrite.html                       | 20 ++++++++++----------
 htdocs/index.html                          |  2 +-
 htdocs/lists.html                          |  2 +-
 htdocs/news/profiledriven.html             |  2 +-
 htdocs/projects/documentation.html         |  2 +-
 htdocs/projects/index.html                 |  2 +-
 htdocs/projects/optimize.html              | 24 ++++++++++++------------
 htdocs/projects/tree-ssa/index.html        | 24 ++++++++++++------------
 htdocs/projects/tree-ssa/tree-browser.html |  2 +-
 htdocs/projects/x86.html                   | 12 ++++++------
 htdocs/search.html                         |  8 ++++----
 24 files changed, 96 insertions(+), 96 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs