===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/backends.html,v
retrieving revision 1.49
@@ -111,8 +111,8 @@
</pre>
<p>For AVR simulator, see <a
-href="http://gcc.gnu.org/ml/gcc/2003-10/msg00027.html">
-http://gcc.gnu.org/ml/gcc/2003-10/msg00027.html</a>.</p>
+href="https://gcc.gnu.org/ml/gcc/2003-10/msg00027.html">
+https://gcc.gnu.org/ml/gcc/2003-10/msg00027.html</a>.</p>
<p>* SPU's float is special; it has the same format as IEEE float but has
an extended range and no infinity or NaNs. SPU's float will not produce
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.69
@@ -129,8 +129,8 @@
<p>There is no established convention on when ChangeLog entries are to
be made for testsuite changes; see messages <a
-href="http://gcc.gnu.org/ml/gcc/2000-09/msg00287.html">1</a> and <a
-href="http://gcc.gnu.org/ml/gcc/2000-09/msg00290.html">2</a>.</p>
+href="https://gcc.gnu.org/ml/gcc/2000-09/msg00287.html">1</a> and <a
+href="https://gcc.gnu.org/ml/gcc/2000-09/msg00290.html">2</a>.</p>
<p>If your change fixes a PR, put <code>PR java/58</code> (where
<code>java/58</code> is the actual number of the PR) at the top
@@ -180,8 +180,8 @@
<code>strrchr</code> are preferred to the old functions
<code>bcmp</code>, <code>bcopy</code>, <code>bzero</code>,
<code>index</code> and <code>rindex</code>; see messages <a
-href="http://gcc.gnu.org/ml/gcc/1998-09/msg01000.html">1</a> and <a
-href="http://gcc.gnu.org/ml/gcc/1998-09/msg01127.html">2</a>. The
+href="https://gcc.gnu.org/ml/gcc/1998-09/msg01000.html">1</a> and <a
+href="https://gcc.gnu.org/ml/gcc/1998-09/msg01127.html">2</a>. The
older functions must no longer be used in GCC; apart from
<code>index</code>, these identifiers are poisoned to prevent their
use.</p>
@@ -225,7 +225,7 @@
their origin: the people who added them or submitted the bug report
they relate to, possibly with a reference to a PR in our bug tracking
system. There are <a
-href="http://gcc.gnu.org/ml/gcc/2000-01/msg00593.html">some copyright
+href="https://gcc.gnu.org/ml/gcc/2000-01/msg00593.html">some copyright
guidelines</a> on what can be included in the testsuite.</p>
<p>If a testcase itself is incorrect, but there's a possibility that an
@@ -713,7 +713,7 @@
<p>Testing for <code>ERROR_MARK</code>s should be done by comparing
against <code>error_mark_node</code> rather than by comparing the
<code>TREE_CODE</code> against <code>ERROR_MARK</code>; see <a
-href="http://gcc.gnu.org/ml/gcc-patches/2000-10/msg00792.html">message</a>.</p>
+href="https://gcc.gnu.org/ml/gcc-patches/2000-10/msg00792.html">message</a>.</p>
<h4><a name="Generated">Parameters Affecting Generated Code</a></h4>
@@ -750,8 +750,8 @@
where the macro is a wrapper for efficiency
that should be considered as a function;
see messages
-<a href="http://gcc.gnu.org/ml/gcc-patches/2000-09/msg00901.html">1</a>
-and <a href="http://gcc.gnu.org/ml/gcc-patches/2000-09/msg00912.html">2</a>.
+<a href="https://gcc.gnu.org/ml/gcc-patches/2000-09/msg00901.html">1</a>
+and <a href="https://gcc.gnu.org/ml/gcc-patches/2000-09/msg00912.html">2</a>.
</p>
<p>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/contributewhy.html,v
retrieving revision 1.7
@@ -131,7 +131,7 @@
<p>Finally, please note that GPL-covered code may <em>not</em> be
distributed under an NDA,
-<a href="http://gcc.gnu.org/ml/gcc/2001-07/msg01342.html">as explained
+<a href="https://gcc.gnu.org/ml/gcc/2001-07/msg01342.html">as explained
by Richard Stallman</a>.</p>
</body>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v
retrieving revision 1.107
@@ -22,11 +22,11 @@
<p>Announcement lists:</p>
<ul>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-announce/">gcc-announce</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-announce/">gcc-announce</a></b>
is a read-only low volume list where
we post announcements about releases or other important events.</li>
- <li><b><a href="http://gcc.gnu.org/ml/java-announce/">java-announce</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/java-announce/">java-announce</a></b>
is a low-volume, moderated, announcements-only list. Only announcements
related to the Java language front end or runtime library are posted
here.</li>
@@ -35,11 +35,11 @@
<p>Open lists:</p>
<ul>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-help/">gcc-help</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-help/">gcc-help</a></b>
is a relatively high volume list for people searching for help in
building or using GCC.</li>
- <li><p><b><a href="http://gcc.gnu.org/ml/gcc/">gcc</a></b>
+ <li><p><b><a href="https://gcc.gnu.org/ml/gcc/">gcc</a></b>
is a high volume list for general development discussions about GCC.
Anything relevant to the development or testing of GCC and not
covered by other mailing lists is suitable for discussion here.</p>
@@ -54,45 +54,45 @@
sufficient to follow the major trends and important news in GCC's
development process.</p></li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-bugs/">gcc-bugs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-bugs/">gcc-bugs</a></b>
is a relatively high volume list with mails from our
bug-tracking system.</li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-patches/">gcc-patches</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-patches/">gcc-patches</a></b>
is a relatively high volume list for patch submissions and discussion of
particular patches. All patches (including those for front ends and web
pages) and all discussion for a particular patch should be sent to this
list.</li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-testresults/">
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-testresults/">
gcc-testresults</a></b> is a moderate volume list where test results for
the GCC compilers are posted.</li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-regression/">gcc-regression</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-regression/">gcc-regression</a></b>
is a moderate volume list where regression results for the GCC compilers
are posted.</li>
- <li><b><a href="http://gcc.gnu.org/ml/libstdc++/">libstdc++</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/libstdc++/">libstdc++</a></b>
is the main discussion and development list for the standard C++
library (libstdc++-v3). Patches to libstdc++-v3 should be sent to
both this list and <b>gcc-patches</b>.</li>
- <li><b><a href="http://gcc.gnu.org/ml/java/">java</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/java/">java</a></b>
is the main discussion and development list for the Java language
front end of GCC, and the corresponding runtime library.</li>
- <li><b><a href="http://gcc.gnu.org/ml/java-patches/">java-patches</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/java-patches/">java-patches</a></b>
is a list for submission and discussion of patches to libgcj, the
Java runtime. Patches to GCJ, the Java language front end, should
go to both this list and <b>gcc-patches</b>.</li>
- <li><b><a href="http://gcc.gnu.org/ml/fortran/">fortran</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/fortran/">fortran</a></b>
is the main discussion and development list for the Fortran language
front end of GCC, and the corresponding runtime library. Patches to
gfortran and libgfortran should go to both this list and
<b>gcc-patches</b>.</li>
- <li><b><a href="http://gcc.gnu.org/ml/jit/">jit</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/jit/">jit</a></b>
is for discussion and development of
<a href="http://gcc.gnu.org/wiki/JIT">libgccjit</a>, an experimental
library for implementing Just-In-Time compilation using GCC as a back end.
@@ -104,29 +104,29 @@
<p>Read only lists:</p>
<ul>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-prs/">gcc-prs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-prs/">gcc-prs</a></b>
is a read-only, relatively high volume list which tracks problem reports
as they are entered into our database.</li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-cvs/">gcc-cvs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-cvs/">gcc-cvs</a></b>
is a read-only, relatively high volume list which tracks checkins to the
GCC SVN repository.</li>
- <li><b><a href="http://gcc.gnu.org/ml/libstdc++-cvs/">libstdc++-cvs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/libstdc++-cvs/">libstdc++-cvs</a></b>
is a read-only, relatively low volume list which tracks checkins to
the libstdc++-v3 part of the GCC SVN repository. This is a subset
of the messages to <b>gcc-cvs</b>.</li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-cvs-wwwdocs/">gcc-cvs-wwwdocs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gcc-cvs-wwwdocs/">gcc-cvs-wwwdocs</a></b>
is a read-only, relatively low volume list which tracks checkins to
the GCC webpages repository.</li>
- <li><b><a href="http://gcc.gnu.org/ml/gccadmin/">gccadmin</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/gccadmin/">gccadmin</a></b>
is a read-only moderate volume list where output from
<code>cron</code> jobs run by the <code>gccadmin</code> account on
gcc.gnu.org is posted.</li>
- <li><b><a href="http://gcc.gnu.org/ml/java-prs/">java-prs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/java-prs/">java-prs</a></b>
is a read-only list which tracks Java-related problem reports as
they are entered into our database. Messages sent here are
also sent to <b>gcc-prs</b>.</li>
@@ -140,7 +140,7 @@
<p>Historical lists (archives only, no longer in use):</p>
<ul>
- <li><b><a href="http://gcc.gnu.org/ml/libstdc++-prs/">libstdc++-prs</a></b>
+ <li><b><a href="https://gcc.gnu.org/ml/libstdc++-prs/">libstdc++-prs</a></b>
was formerly used by the libstdc++-v3 problem report database.
libstdc++-v3 now uses the main GCC database and the <b>gcc-prs</b> list.</li>
</ul>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v
retrieving revision 1.139
@@ -89,7 +89,7 @@
language from C to <a href="codingconventions.html#Cxx_Conventions">C++</a>.
Additionally, some data structures have been re-implemented in C++
(more details in the <a
-href="http://gcc.gnu.org/ml/gcc-patches/2012-08/msg00711.html">merge
+href="https://gcc.gnu.org/ml/gcc-patches/2012-08/msg00711.html">merge
announcement</a>). This work was contributed by Lawrence Crowl and
Diego Novillo of Google.</dd>
@@ -360,11 +360,11 @@
<dt>January 8, 2008</dt>
<dd>Jakub Jelinek, Joseph Myers, and Richard Guenther <a
-href="http://gcc.gnu.org/ml/gcc/2008-01/msg00133.html">join the GCC
+href="https://gcc.gnu.org/ml/gcc/2008-01/msg00133.html">join the GCC
release management team</a>, quadrupling its head count.</dd>
<dt>January 2, 2008</dt>
-<dd><a href="http://gcc.gnu.org/ml/gcc/2008-01/msg00009.html">Gfortran
+<dd><a href="https://gcc.gnu.org/ml/gcc/2008-01/msg00009.html">Gfortran
annual report for 2008</a></dd>
<dt>October 7, 2007</dt>
@@ -446,7 +446,7 @@
<dd><a href="http://gcc.gnu.org/wiki/mem-ssa">Memory SSA</a>, a new
representation for memory expressions in SSA form has been contributed
by Diego Novillo of Red Hat. This new mechanism improves <a
-href="http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00436.html">compile-times
+href="https://gcc.gnu.org/ml/gcc-patches/2006-12/msg00436.html">compile-times
and memory utilization</a> by the compiler.</dd>
<dt>January 3, 2007</dt>
@@ -456,7 +456,7 @@
<dt>January 1, 2007</dt>
<dd>2006 has been a very productive year for the new Fortran frontend,
- with <a href="http://gcc.gnu.org/ml/gcc/2007-01/msg00059.html">lots
+ with <a href="https://gcc.gnu.org/ml/gcc/2007-01/msg00059.html">lots
of improvements and fixes</a>.</dd>
<dt>September 5, 2006</dt>
@@ -616,7 +616,7 @@
<dd>
The <a href="http://gcc.gnu.org/projects/tree-ssa/">tree-ssa
branch</a> has been <a
-href="http://gcc.gnu.org/ml/gcc/2004-05/msg00679.html">merged into
+href="https://gcc.gnu.org/ml/gcc/2004-05/msg00679.html">merged into
mainline</a>.
</dd>
@@ -743,7 +743,7 @@
<dt><b>December 27, 2002</b></dt>
<dd>
Mark Mitchell of CodeSourcery has contributed a
-<a href="http://gcc.gnu.org/ml/gcc/2000-10/msg00573.html">new, hand-crafted
+<a href="https://gcc.gnu.org/ml/gcc/2000-10/msg00573.html">new, hand-crafted
recursive-descent C++ parser</a> sponsored by the Los Alamos National
Laboratory. The new parser is more standard conforming and fixes many bugs
(about 100 in our bug database alone) from the old YACC-derived parser.
@@ -751,7 +751,7 @@
<dt><b>December 4, 2002</b></dt>
<dd>
-Nathan Sidwell of CodeSourcery has contributed an <a href="http://gcc.gnu.org/ml/gcc-patches/2002-11/msg01858.html">implementation of
+Nathan Sidwell of CodeSourcery has contributed an <a href="https://gcc.gnu.org/ml/gcc-patches/2002-11/msg01858.html">implementation of
non-trivial covariant returns for non-varadic virtual functions</a>.
</dd>
@@ -962,7 +962,7 @@
<dd>
Our CVS tree has branched for the GCC 3.0 release process and Mark Mitchell,
our release manager, has provided some <a
-href="http://gcc.gnu.org/ml/gcc/2001-02/msg00403.html">guidelines for the
+href="https://gcc.gnu.org/ml/gcc/2001-02/msg00403.html">guidelines for the
GCC 3.0 branch</a>.
</dd>
@@ -1433,7 +1433,7 @@
<dt><b>April 13, 1999</b></dt>
<dd>
We have set up a new <a href="lists.html">mailing list</a>
-<a href="http://gcc.gnu.org/ml/gcc-cvs-wwwdocs/">gcc-cvs-wwwdocs</a>
+<a href="https://gcc.gnu.org/ml/gcc-cvs-wwwdocs/">gcc-cvs-wwwdocs</a>
that tracks checkins to the egcs webpages CVS repository.
</dd>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/simtest-howto.html,v
retrieving revision 1.28
@@ -154,9 +154,9 @@
<td>arm-sim</td>
<td>32-bit word, little endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00592.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00592.html">3.3 20030509 (prerelease)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00949.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00949.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
@@ -165,7 +165,7 @@
<td>fr30-sim</td>
<td>32-bit word, big endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00766.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00766.html">3.3 20030509 (prerelease)</a>
</td>
</tr>
@@ -174,9 +174,9 @@
<td>h8300-sim</td>
<td>cc0 target, big endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00624.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00624.html">3.3 20030509 (prerelease)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00967.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00967.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
@@ -185,7 +185,7 @@
<td>m32r-sim</td>
<td>32-bit word, big endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg01478.html">3.3</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg01478.html">3.3</a>
</td>
</tr>
@@ -194,9 +194,9 @@
<td>mips-sim</td>
<td>big endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2005-11/msg00636.html">4.1.0 20051112 (experimental)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2005-11/msg00636.html">4.1.0 20051112 (experimental)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00619.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00619.html">3.3 20030509 (prerelease)</a>
</td>
</tr>
@@ -205,7 +205,7 @@
<td>mips-sim-idt64</td>
<td> </td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-06/msg00335.html">3.4 20030605 (experimental)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-06/msg00335.html">3.4 20030605 (experimental)</a>
</td>
</tr>
@@ -214,9 +214,9 @@
<td>mn10300-sim</td>
<td>cc0 target, little endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00632.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00632.html">3.3 20030509 (prerelease)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00972.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00972.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
@@ -225,7 +225,7 @@
<td>powerpc-sim</td>
<td>32-bit word, big endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-03/msg00033.html">3.4 20030301 (experimental)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-03/msg00033.html">3.4 20030301 (experimental)</a>
</td>
</tr>
@@ -234,9 +234,9 @@
<td>sh-hms</td>
<td> </td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00622.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00622.html">3.3 20030509 (prerelease)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00964.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00964.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
@@ -245,13 +245,13 @@
<td>sh-sim</td>
<td>big endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01441.html">4.2.0 20060226 (experimental)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2006-02/msg01441.html">4.2.0 20060226 (experimental)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-06/msg00315.html">3.4 20030605 (experimental)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-06/msg00315.html">3.4 20030605 (experimental)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00631.html">3.3 20030509 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00631.html">3.3 20030509 (prerelease)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00970.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00970.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
@@ -260,9 +260,9 @@
<td>sparc-sim</td>
<td> </td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00587.html">3.3 20030507 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00587.html">3.3 20030507 (prerelease)</a>
<br />
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00942.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00942.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
@@ -271,7 +271,7 @@
<td>v850-sim</td>
<td>cc0 target, 32-bit word, little endian</td>
<td>
- <a href="http://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00978.html">3.2.3 20030415 (prerelease)</a>
+ <a href="https://gcc.gnu.org/ml/gcc-testresults/2003-04/msg00978.html">3.2.3 20030415 (prerelease)</a>
</td>
</tr>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svnwrite.html,v
retrieving revision 1.30
@@ -140,7 +140,7 @@
<p>When you have checked in a patch exactly as it has been approved,
you do not need to tell that to people -- including the approver.
People interested in when a particular patch is committed can check
-SVN or the <a href="http://gcc.gnu.org/ml/gcc-cvs/">gcc-cvs</a>
+SVN or the <a href="https://gcc.gnu.org/ml/gcc-cvs/">gcc-cvs</a>
list.</p>
<h3>Free for all</h3>