@@ -10,9 +10,8 @@
<h1>GCC Coding Conventions</h1>
<p>There are some additional coding conventions for code in GCC,
-beyond those in the <a
-href="http://www.gnu.org/prep/standards_toc.html">GNU Coding
-Standards</a>. Some existing code may not follow these conventions,
+beyond those in the <a href="https://www.gnu.org/prep/standards/">GNU
+Coding Standards</a>. Some existing code may not follow these conventions,
but they must be used for new code. If changing existing
code to follow these conventions, it is best to send changes to follow
the conventions separately from any other changes to the code.</p>
@@ -62,11 +62,10 @@ copyright assignment on file.</p>
<h2 id="standards">Coding Standards</h2>
<p>All contributions must conform to the <a
-href="http://www.gnu.org/prep/standards_toc.html">GNU Coding
-Standards</a>. There are also some <a
-href="codingconventions.html">additional coding conventions for
-GCC</a>; these include documentation and testsuite requirements as
-well as requirements on code formatting.</p>
+href="https://www.gnu.org/prep/standards/">GNU Coding Standards</a>.
+There are also some <a href="codingconventions.html">additional coding
+conventions for GCC</a>; these include documentation and testsuite
+requirements as well as requirements on code formatting.</p>
<p>Submissions which do not conform to the standards will be returned
with a request to address any such problems. To help with the