GCC Snapshots

We recommend that you use SVN to access our current development sources.

We also make regular snapshots available for FTP download from our mirror sites about once a week. These snapshots are intended to give everyone access to work in progress. Any given snapshot may generate incorrect code or even fail to build.

If you plan on downloading and using snapshots, we highly recommend you subscribe to the GCC mailing lists. See mailing lists on the main GCC page for instructions on how to subscribe.

When using the diff files to update from older snapshots to newer snapshots, make sure to use "-E" and "-p" arguments to patch so that empty files are deleted and full pathnames are provided to patch. If your version of patch does not support "-E", you'll need to get a newer version. Also note that you may need autoconf, autoheader and various other programs if you use diff files to update from one snapshot to the next.

contrib/gcc_update can be used to apply diffs between successive snapshot versions and preserve relations between generated files so that autoconf et al aren't needed. This is documented in comments in contrib/gcc_update.

The program sha512sum — which is included with the GNU Coreutils — can be used to verify the integrity of a snapshot or release. The release script generates the file sha512.sum that provides a 512-bit checksum for the tarball and other files in the snapshot directory.  Use the following command to verify the sources:
sha512sum --check --ignore-missing sha512.sum