The checksum file uses SHA512 not MD5SUM, so the instructions should be updated accordingly.
SInce there's only one tarfile these days (not separate ones for gcc-base, gcc-g++, gcc-fortran, etc) it doesn't seem necessary to filter out the "OK" lines with grep, but I could add --quiet to the command if we want that. I added --ignore-missing because I doubt most people also download the README and index.html files, so the option avoids gettings warnings about those files. OK for CVS?
Index: htdocs/snapshots.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/snapshots.html,v retrieving revision 1.24 diff -u -r1.24 snapshots.html --- htdocs/snapshots.html 30 Sep 2018 14:38:47 -0000 1.24 +++ htdocs/snapshots.html 14 Mar 2019 11:42:57 -0000 @@ -35,15 +35,15 @@ files so that autoconf et al aren't needed. This is documented in comments in contrib/gcc_update.</p> -<p>The program <code>md5sum</code> — which is included with the +<p>The program <code>sha512sum</code> — which is included with the <a href="https://www.gnu.org/software/coreutils/";>GNU Coreutils</a> — can be used to verify the integrity of a snapshot or release. The release script generates the file -<code>MD5SUMS</code> that provides a 128-bit checksum for every -file in the tarball. Use the following command to verify the -sources:<br /> +<code>sha512.sum</code> that provides a 512-bit checksum for the tarball +and other files in the snapshot directory. Use the following command +to verify the sources:<br /> -<code>md5sum --check MD5SUMS | grep -v OK$</code></p> +<code>sha512sum --check --ignore-missing sha512.sum</code></p> <!-- <p>In addition, some of our contributors also provide pre-built binaries
