This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[wwwdocs] */changes.html -- replace <a name=...> by id attributes
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Sun, 26 Aug 2018 15:14:12 +0200 (CEST)
- Subject: [wwwdocs] */changes.html -- replace <a name=...> by id attributes
More of the same, though this a bit more involved since we cannot use
version numbers as ids (which may not start with a digit unfortunately).
Committed.
Gerald
Replace <a name=...> by id attributes. Use GCCX.Y instead of X.Y
for ids since those must not start with a digit.
Index: gcc-3.1/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.1/changes.html,v
retrieving revision 1.75
diff -u -r1.75 changes.html
--- gcc-3.1/changes.html 2 Jun 2018 21:16:14 -0000 1.75
+++ gcc-3.1/changes.html 26 Aug 2018 11:18:31 -0000
@@ -319,7 +319,7 @@
</ul>
-<h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+<h2 id="obsolete_systems">Obsolete Systems</h2>
<p>Support for a number of older systems has been declared obsolete in
GCC 3.1. Unless there is activity to revive them, the next release of
Index: gcc-3.2/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/changes.html,v
retrieving revision 1.58
diff -u -r1.58 changes.html
--- gcc-3.2/changes.html 2 Jun 2018 21:16:14 -0000 1.58
+++ gcc-3.2/changes.html 26 Aug 2018 11:18:32 -0000
@@ -95,7 +95,7 @@
<!-- Changes for later point releases should be added at the top. -->
<hr />
-<h2><a name="3.2.3">GCC 3.2.3</a></h2>
+<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
were not present in GCC 3.2.2.</p>
@@ -226,7 +226,7 @@
</ul>
<hr />
-<h2><a name="3.2.2">GCC 3.2.2</a></h2>
+<h2 id="GCC3.2.2">GCC 3.2.2</h2>
<p>Beginning with 3.2.2, GCC's Makefile suite supports redirection of
<code>make install</code> by means of the <code>DESTDIR</code>
@@ -361,7 +361,7 @@
</ul>
<hr />
-<h2><a name="3.2.1">GCC 3.2.1</a></h2>
+<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
C++ generates code that is known not to be binary-compatible with the
@@ -553,7 +553,7 @@
</ul>
<hr />
-<h2><a name="3.2">GCC 3.2</a></h2>
+<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
binary interface (ABI), hence the change to the second part of the version
Index: gcc-3.3/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.3/changes.html,v
retrieving revision 1.63
diff -u -r1.63 changes.html
--- gcc-3.3/changes.html 2 Jun 2018 21:16:15 -0000 1.63
+++ gcc-3.3/changes.html 26 Aug 2018 11:18:33 -0000
@@ -131,14 +131,14 @@
work correctly.</li>
<li>A new function attribute,
- <code><a name="nonnull_attribute">nonnull</a></code>, has been added
+ <code id="nonnull_attribute">nonnull</code>, has been added
which allows pointer arguments to functions to be specified as
requiring a non-null value. The compiler currently uses this
information to issue a warning when it detects a null value passed
in such an argument slot.</li>
<li>A new type attribute,
- <code><a name="may_alias">may_alias</a></code>, has been added.
+ <code id="may_alias">may_alias</code>, has been added.
Accesses to objects with types with this attribute are not
subjected to type-based alias analysis, but are instead assumed to
be able to alias any other type of objects, just like the
@@ -300,7 +300,7 @@
</ul>
-<h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+<h2 id="obsolete_systems">Obsolete Systems</h2>
<p>Support for a number of older systems has been declared obsolete in
GCC 3.3. Unless there is activity to revive them, the next release of
@@ -704,7 +704,7 @@
</ul>
<hr />
-<h2><a name="3.3.1">GCC 3.3.1</a></h2>
+<h2 id="GCC3.3.1">GCC 3.3.1</h2>
<h3>Bug Fixes</h3>
@@ -913,7 +913,7 @@
</ul>
<hr />
-<h2><a name="3.3.2">GCC 3.3.2</a></h2>
+<h2 id="GCC3.3.2">GCC 3.3.2</h2>
<h3>Bug Fixes</h3>
@@ -1044,7 +1044,7 @@
</ul>
<hr />
-<h2><a name="3.3.3">GCC 3.3.3</a></h2>
+<h2 id="GCC3.3.3">GCC 3.3.3</h2>
<h3>Minor features</h3>
<p>In addition to the bug fixes documented below, this release
@@ -1273,7 +1273,7 @@
<hr />
-<h2><a name="3.3.4">GCC 3.3.4</a></h2>
+<h2 id="GCC3.3.4">GCC 3.3.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.3.4">list
@@ -1284,7 +1284,7 @@
<hr />
-<h2><a name="3.3.5">GCC 3.3.5</a></h2>
+<h2 id="GCC3.3.5">GCC 3.3.5</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.3.5">list
@@ -1295,7 +1295,7 @@
<hr />
-<h2><a name="3.3.6">GCC 3.3.6</a></h2>
+<h2 id="GCC3.3.6">GCC 3.3.6</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.3.6">list
Index: gcc-3.4/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.4/changes.html,v
retrieving revision 1.166
diff -u -r1.166 changes.html
--- gcc-3.4/changes.html 2 Jun 2018 21:16:15 -0000 1.166
+++ gcc-3.4/changes.html 26 Aug 2018 11:18:35 -0000
@@ -1129,7 +1129,7 @@
<code>-mno-serialize-volatile</code> option is no longer supported.</li>
</ul>
-<h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+<h2 id="obsolete_systems">Obsolete Systems</h2>
<p>Support for a number of older systems has been declared obsolete in
GCC 3.4. Unless there is activity to revive them, the next release of
@@ -1217,7 +1217,7 @@
</ul>
<hr />
-<h2><a name="3.4.0">GCC 3.4.0</a></h2>
+<h2 id="GCC3.4.0">GCC 3.4.0</h2>
<h3>Bug Fixes</h3>
@@ -1231,7 +1231,7 @@
in 3.4.0 that are not flagged as 3.4 regressions.</p>
<hr />
-<h2><a name="3.4.1">GCC 3.4.1</a></h2>
+<h2 id="3.4.1">GCC 3.4.1</h2>
<h3>Bug Fixes</h3>
@@ -1455,7 +1455,7 @@
</ul>
<hr />
-<h2><a name="3.4.2">GCC 3.4.2</a></h2>
+<h2 id="GCC3.4.2">GCC 3.4.2</h2>
<h3>Bug Fixes</h3>
@@ -1606,7 +1606,7 @@
</ul>
<hr />
-<h2><a name="3.4.3">GCC 3.4.3</a></h2>
+<h2 id="GCC3.4.3">GCC 3.4.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.3">list
@@ -1731,7 +1731,7 @@
<hr />
-<h2><a name="3.4.4">GCC 3.4.4</a></h2>
+<h2 id="GCC3.4.4">GCC 3.4.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.4">list
@@ -1742,7 +1742,7 @@
<hr />
-<h2><a name="3.4.5">GCC 3.4.5</a></h2>
+<h2 id="GCC3.4.5">GCC 3.4.5</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.5">list
@@ -2002,7 +2002,7 @@
<hr />
-<h2><a name="3.4.6">GCC 3.4.6</a></h2>
+<h2 id="GCC3.4.6">GCC 3.4.6</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=3.4.6">list
Index: gcc-4.0/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.72
diff -u -r1.72 changes.html
--- gcc-4.0/changes.html 2 Jun 2018 21:16:15 -0000 1.72
+++ gcc-4.0/changes.html 26 Aug 2018 11:18:35 -0000
@@ -533,7 +533,7 @@
systems, which NetWare never tried to support).</li>
</ul>
-<h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+<h2 id="obsolete_systems">Obsolete Systems</h2>
<p>Support for a number of older systems has been declared obsolete in
GCC 4.0. Unless there is activity to revive them, the next release of
@@ -570,7 +570,7 @@
about locations of variables and they allow debugging code compiled
with <code>-fomit-frame-pointer</code>.</li>
- <li><a name="visibility">The <code>-fvisibility</code> option</a> has
+ <li id="visibility">The <code>-fvisibility</code> option has
been added which allows the default ELF visibility of all symbols to be
set per compilation and the new <code>#pragma GCC visibility</code>
preprocessor command allows the setting of default ELF visibility for a
@@ -593,7 +593,7 @@
</ul>
<hr />
-<h2><a name="4.0.1">GCC 4.0.1</a></h2>
+<h2 id="GCC4.0.1">GCC 4.0.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.0.1">list
@@ -602,7 +602,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.0.2">GCC 4.0.2</a></h2>
+<h2 id="GCC4.0.2">GCC 4.0.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.0.2">list
@@ -621,7 +621,7 @@
corrected in the current 4.0 branch sources and will not be present in
GCC 4.0.3.</p>
-<h2><a name="4.0.3">GCC 4.0.3</a></h2>
+<h2 id="GCC4.0.3">GCC 4.0.3</h2>
<p>Starting with this release, the function <code>getcontext</code> is
recognized by the compiler as having the same semantics as the
@@ -630,7 +630,7 @@
a warning about the variables that may be clobbered after the second
return from the function.</p>
-<h2><a name="4.0.4">GCC 4.0.4</a></h2>
+<h2 id="GCC4.0.4">GCC 4.0.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.0.4">list
Index: gcc-4.1/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.1/changes.html,v
retrieving revision 1.31
diff -u -r1.31 changes.html
--- gcc-4.1/changes.html 2 Jun 2018 21:16:15 -0000 1.31
+++ gcc-4.1/changes.html 26 Aug 2018 11:18:35 -0000
@@ -654,7 +654,7 @@
<li>Support has been added for this new architecture.</li>
</ul>
-<h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+<h2 id="obsolete_systems">Obsolete Systems</h2>
<h2>Documentation improvements</h2>
@@ -672,7 +672,7 @@
should not experience any measurable slowdown.</li>
</ul>
-<h2><a name="4.1.2">GCC 4.1.2</a></h2>
+<h2 id="GCC4.1.2">GCC 4.1.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.1.2">list
Index: gcc-4.2/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.2/changes.html,v
retrieving revision 1.44
diff -u -r1.44 changes.html
--- gcc-4.2/changes.html 2 Jun 2018 21:16:16 -0000 1.44
+++ gcc-4.2/changes.html 26 Aug 2018 11:18:35 -0000
@@ -348,7 +348,7 @@
</ul>
-<h2><a name="obsolete_systems">Obsolete Systems</a></h2>
+<h2 id="obsolete_systems">Obsolete Systems</h2>
<h2>Documentation improvements</h2>
Index: gcc-4.3/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.3/changes.html,v
retrieving revision 1.134
diff -u -r1.134 changes.html
--- gcc-4.3/changes.html 14 Jul 2018 21:02:05 -0000 1.134
+++ gcc-4.3/changes.html 26 Aug 2018 11:18:36 -0000
@@ -989,7 +989,7 @@
for reporting bugs in their versions of GCC.</li>
</ul>
-<h2><a name="4.3.1">GCC 4.3.1</a></h2>
+<h2 id="GCC4.3.1">GCC 4.3.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.1">list
@@ -1017,7 +1017,7 @@
the <code>--enable-cld</code> configure option.</li>
</ul>
-<h2><a name="4.3.2">GCC 4.3.2</a></h2>
+<h2 id="GCC4.3.2">GCC 4.3.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.2">list
@@ -1026,7 +1026,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.3.3">GCC 4.3.3</a></h2>
+<h2 id="GCC4.3.3">GCC 4.3.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.3">list
@@ -1035,7 +1035,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.3.4">GCC 4.3.4</a></h2>
+<h2 id="GCC4.3.4">GCC 4.3.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.4">list
@@ -1044,7 +1044,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.3.5">GCC 4.3.5</a></h2>
+<h2 id="GCC4.3.5">GCC 4.3.5</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.5">list
@@ -1053,7 +1053,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.3.6">GCC 4.3.6</a></h2>
+<h2 id="GCC4.3.6">GCC 4.3.6</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.3.6">list
Index: gcc-4.4/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.4/changes.html,v
retrieving revision 1.91
diff -u -r1.91 changes.html
--- gcc-4.4/changes.html 2 Jun 2018 21:16:16 -0000 1.91
+++ gcc-4.4/changes.html 26 Aug 2018 11:18:37 -0000
@@ -718,7 +718,7 @@
<h2>Other significant improvements</h2>
-<h2><a name="4.4.1">GCC 4.4.1</a></h2>
+<h2 id="GCC4.4.1">GCC 4.4.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.1">list
@@ -727,7 +727,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.4.2">GCC 4.4.2</a></h2>
+<h2 id="GCC4.4.2">GCC 4.4.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.2">list
@@ -736,7 +736,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.4.3">GCC 4.4.3</a></h2>
+<h2 id="GCC4.4.3">GCC 4.4.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.3">list
@@ -745,7 +745,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.4.4">GCC 4.4.4</a></h2>
+<h2 id="GCC4.4.4">GCC 4.4.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.4">list
@@ -754,7 +754,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.4.5">GCC 4.4.5</a></h2>
+<h2 id="GCC4.4.5">GCC 4.4.5</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.5">list
@@ -763,7 +763,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.4.6">GCC 4.4.6</a></h2>
+<h2 id="GCC4.4.6">GCC 4.4.6</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.6">list
@@ -772,7 +772,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.4.7">GCC 4.4.7</a></h2>
+<h2 id="GCC4.4.7">GCC 4.4.7</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.4.7">list
Index: gcc-4.5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v
retrieving revision 1.119
diff -u -r1.119 changes.html
--- gcc-4.5/changes.html 2 Jun 2018 21:16:16 -0000 1.119
+++ gcc-4.5/changes.html 26 Aug 2018 11:18:37 -0000
@@ -448,7 +448,7 @@
if the default would normally be to link it dynamically.</li>
</ul>
-<h3><a name="Fortran">Fortran</a></h3>
+<h3 id="Fortran">Fortran</h3>
<ul>
<li>The <code>COMMON</code> default padding has been changed –
instead of adding the padding before a variable it is now added
@@ -837,7 +837,7 @@
</li>
</ul>
-<h2><a name="4.5.1">GCC 4.5.1</a></h2>
+<h2 id="GCC4.5.1">GCC 4.5.1</h2>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.1">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -861,7 +861,7 @@
you should configure with the <code>--enable-lto</code> option.</p></li>
</ul>
-<h2><a name="4.5.2">GCC 4.5.2</a></h2>
+<h2 id="GCC4.5.2">GCC 4.5.2</h2>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.2">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -869,7 +869,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.5.3">GCC 4.5.3</a></h2>
+<h2 id="GCC4.5.3">GCC 4.5.3</h2>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.3">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -887,7 +887,7 @@
new builtin functions <code>vec_vsx_ld</code> and <code>vec_vsx_st</code> which
always generates the VSX memory instructions.</p>
-<h2><a name="4.5.4">GCC 4.5.4</a></h2>
+<h2 id="GCC4.5.4">GCC 4.5.4</h2>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.5.4">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
Index: gcc-4.6/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v
retrieving revision 1.156
diff -u -r1.156 changes.html
--- gcc-4.6/changes.html 2 Jun 2018 21:16:16 -0000 1.156
+++ gcc-4.6/changes.html 26 Aug 2018 11:18:38 -0000
@@ -1140,7 +1140,7 @@
</li>
</ul>
-<h2><a name="4.6.1">GCC 4.6.1</a></h2>
+<h2 id="GCC4.6.1">GCC 4.6.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.6.1">list
@@ -1149,7 +1149,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.6.2">GCC 4.6.2</a></h2>
+<h2 id="GCC4.6.2">GCC 4.6.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.6.2">list
@@ -1158,7 +1158,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.6.3">GCC 4.6.3</a></h2>
+<h2 id="GCC4.6.3">GCC 4.6.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.6.3">list
@@ -1167,7 +1167,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.6.4">GCC 4.6.4</a></h2>
+<h2 id="GCC4.6.4">GCC 4.6.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.6.4">list
Index: gcc-4.7/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.149
diff -u -r1.149 changes.html
--- gcc-4.7/changes.html 15 Jul 2018 05:55:48 -0000 1.149
+++ gcc-4.7/changes.html 26 Aug 2018 11:18:38 -0000
@@ -399,8 +399,7 @@
</li>
</ul>
-<a name="cxx" />
-<h3>C++</h3>
+<h3 id="cxx">C++</h3>
<ul>
<li>G++ now accepts the <code>-std=c++11</code>,
@@ -1007,7 +1006,7 @@
</li>
</ul>
-<h2><a name="4.7.1">GCC 4.7.1</a></h2>
+<h2 id="GCC4.7.1">GCC 4.7.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.1">list
@@ -1020,7 +1019,7 @@
the <a href="https://golang.org/doc/go1">Go 1 language
standard.</a></p>
-<h2><a name="4.7.2">GCC 4.7.2</a></h2>
+<h2 id="4.7.2">GCC 4.7.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.2">list
@@ -1029,7 +1028,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.7.3">GCC 4.7.3</a></h2>
+<h2 id="GCC4.7.3">GCC 4.7.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.3">list
@@ -1038,7 +1037,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.7.4">GCC 4.7.4</a></h2>
+<h2 id="GCC4.7.4">GCC 4.7.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.7.4">list
Index: gcc-4.8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.140
diff -u -r1.140 changes.html
--- gcc-4.8/changes.html 2 Jun 2018 21:16:17 -0000 1.140
+++ gcc-4.8/changes.html 26 Aug 2018 11:18:39 -0000
@@ -893,7 +893,7 @@
-->
-<h2><a name="4.8.1">GCC 4.8.1</a></h2>
+<h2 id="GCC4.8.1">GCC 4.8.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.1">list
@@ -922,7 +922,7 @@
<code>--enable-libstdcxx-time=</code> configuration option needs to be
recompiled.</p>
-<h2><a name="4.8.2">GCC 4.8.2</a></h2>
+<h2 id="GCC4.8.2">GCC 4.8.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.2">list
@@ -931,7 +931,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.8.3">GCC 4.8.3</a></h2>
+<h2 id="GCC4.8.3">GCC 4.8.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.3">list
@@ -943,7 +943,7 @@
<p>Support for the new powerpc64le-linux platform has been added. It
defaults to generating code that conforms to the ELFV2 ABI.</p>
-<h2><a name="4.8.4">GCC 4.8.4</a></h2>
+<h2 id="GCC4.8.4">GCC 4.8.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.4">list
@@ -952,7 +952,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.8.5">GCC 4.8.5</a></h2>
+<h2 id="GCC4.8.5">GCC 4.8.5</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.5">list
Index: gcc-4.9/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.92
diff -u -r1.92 changes.html
--- gcc-4.9/changes.html 2 Jun 2018 21:16:17 -0000 1.92
+++ gcc-4.9/changes.html 26 Aug 2018 11:18:39 -0000
@@ -745,7 +745,7 @@
-->
-<h2><a name="4.9.1">GCC 4.9.1</a></h2>
+<h2 id="GCC4.9.1">GCC 4.9.1</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.1">list
@@ -757,7 +757,7 @@
<p>Version 4.0 of the OpenMP specification is supported even in Fortran,
not just C and C++.</p>
-<h2><a name="4.9.2">GCC 4.9.2</a></h2>
+<h2 id="GCC4.9.2">GCC 4.9.2</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.2">list
@@ -766,7 +766,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.9.3">GCC 4.9.3</a></h2>
+<h2 id="GCC4.9.3">GCC 4.9.3</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.3">list
@@ -775,7 +775,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h2><a name="4.9.4">GCC 4.9.4</a></h2>
+<h2 id="GCC4.9.4">GCC 4.9.4</h2>
<p>This is the <a
href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.9.4">list
Index: gcc-5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.150
diff -u -r1.150 changes.html
--- gcc-5/changes.html 2 Jun 2018 21:16:17 -0000 1.150
+++ gcc-5/changes.html 26 Aug 2018 11:18:40 -0000
@@ -985,7 +985,7 @@
</ul>
-<h1><a name="5.2">GCC 5.2</a></h1>
+<h1 id="GCC5.2">GCC 5.2</h1>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.2">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -1038,7 +1038,7 @@
header file needs to be included.</li>
</ul>
-<h1><a name="5.3">GCC 5.3</a></h1>
+<h1 id="GCC5.3">GCC 5.3</h1>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.3">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -1063,7 +1063,7 @@
compile larger GO applications on IBM z Systems.</li>
</ul>
-<h1><a name="5.4">GCC 5.4</a></h1>
+<h1 id="GCC5.4">GCC 5.4</h1>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.4">list
of problem reports (PRs)</a> from GCC's bug tracking system that are
@@ -1071,7 +1071,7 @@
complete (that is, it is possible that some PRs that have been fixed
are not listed here).</p>
-<h1><a name="5.5">GCC 5.5</a></h1>
+<h1 id="GCC5.5">GCC 5.5</h1>
<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=5.5">list
of problem reports (PRs)</a> from GCC's bug tracking system that are