===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/reghunt.html,v
retrieving revision 1.19
@@ -52,7 +52,7 @@
<p>The first three steps are described below. They can be automated,
as can the framework for the binary search. The directory <a
-href="http://gcc.gnu.org/svn/gcc/trunk/contrib/reghunt/">
+href="https://gcc.gnu.org/svn/gcc/trunk/contrib/reghunt/">
<code>contrib/reghunt</code></a> in the GCC repository includes
scripts to do this work.</p>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.70
@@ -165,7 +165,7 @@
C code should avoid pre-standard style function definitions, unnecessary
function prototypes and use of the now deprecated <code>PARAMS</code> macro.
See <a
-href="http://gcc.gnu.org/cgi-bin/cvsweb.cgi/~checkout~/gcc/gcc/README.Portability?content-type=text/plain&only_with_tag=HEAD">README.Portability</a>
+href="https://gcc.gnu.org/svn/gcc/trunk/gcc/README.Portability">README.Portability</a>
for details of some of the portability problems that may arise. Some
of these problems are warned about by <code>gcc -Wtraditional</code>,
which is included in the default warning options in a bootstrap.