<html>
+
<head>
<title>GCC Snapshots</title>
</head>
<body>
<h1>GCC Snapshots</h1>
-<hr>
-The <a href ="http://gcc.gnu.org/">GCC Project</a> makes
+<hr />
+
+<p>The <a href ="http://gcc.gnu.org/">GCC Project</a> makes
periodic snapshots of the GCC source tree available to the public
-for testing purposes.
+for testing purposes.</p>
-If you are planning to download and use one of our snapshots, then
+<p>If you are planning to download and use one of our snapshots, then
we highly recommend you join the GCC developers list. Details for
-how to sign up can be found on the GCC project home page.
+how to sign up can be found on the GCC project home page.</p>
<blockquote>
- <p> <a href="@LONG_DATE@/gcc-@DATE@.tar.gz">
+ <p> <a href="@LONG_DATE@/gcc-@DATE@.tar.bz2">
gcc</a> @TEXT_DATE@ snapshot, includes all languages.
- <p> <a href="@LONG_DATE@/gcc-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-@LAST_DATE@-@DATE@.diff.bz2">
gcc-@LAST_DATE@-@DATE@</a> patch file to bring gcc-@LAST_DATE@ up to
gcc-@DATE@.
- <p> <a href="@LONG_DATE@/gcc-core-@DATE@.tar.gz">
+ <p> <a href="@LONG_DATE@/gcc-core-@DATE@.tar.bz2">
gcc-core</a> @TEXT_DATE@ snapshot, includes just the C front
end and core compiler.
- <p> <a href="@LONG_DATE@/gcc-core-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-core-@LAST_DATE@-@DATE@.diff.bz2">
gcc-core-@LAST_DATE@-@DATE@</a> patch file to bring gcc-core-@LAST_DATE@
up to gcc-core-@DATE@.
- <p> <a href="@LONG_DATE@/gcc-g++-@DATE@.tar.gz">
- gcc-g++</a> @TEXT_DATE@ snapshot, includes just the G++ front
+ <p> <a href="@LONG_DATE@/gcc-g++-@DATE@.tar.bz2">
+ gcc-g++</a> @TEXT_DATE@ snapshot, includes just the C++ front
end and runtime.
- <p> <a href="@LONG_DATE@/gcc-g++-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-g++-@LAST_DATE@-@DATE@.diff.bz2">
gcc-g++-@LAST_DATE@-@DATE@</a> patch file to bring gcc-g++-@LAST_DATE@
up to gcc-g++-@DATE@.
- <p> <a href="@LONG_DATE@/gcc-g77-@DATE@.tar.gz">
- gcc-g77</a> @TEXT_DATE@ snapshot, includes just the G77 front
+ <p> <a href="@LONG_DATE@/gcc-g77-@DATE@.tar.bz2">
+ gcc-g77</a> @TEXT_DATE@ snapshot, includes just the F77 front
end and runtime.
- <p> <a href="@LONG_DATE@/gcc-g77-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-g77-@LAST_DATE@-@DATE@.diff.bz2">
gcc-g77-@LAST_DATE@-@DATE@</a> patch file to bring gcc-g77-@LAST_DATE@
up to gcc-g77-@DATE@.
- <p> <a href="@LONG_DATE@/gcc-java-@DATE@.tar.gz">
+ <p> <a href="@LONG_DATE@/gcc-java-@DATE@.tar.bz2">
gcc-java</a> @TEXT_DATE@ snapshot, includes just the Java
- front end.
+ front end and runtime.
- <p> <a href="@LONG_DATE@/gcc-java-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-java-@LAST_DATE@-@DATE@.diff.bz2">
gcc-java-@LAST_DATE@-@DATE@</a> patch file to bring gcc-java-@LAST_DATE@
up to gcc-java-@DATE@.
- <p> <a href="@LONG_DATE@/gcc-chill-@DATE@.tar.gz">
- gcc-chill</a> @TEXT_DATE@ snapshot, includes just the Chill
- front end and runtime.
-
- <p> <a href="@LONG_DATE@/gcc-chill-@LAST_DATE@-@DATE@.diff.gz">
- gcc-chill-@LAST_DATE@-@DATE@</a> patch file to bring gcc-chill-@LAST_DATE@
- up to gcc-chill-@DATE@.
-
- <p> <a href="@LONG_DATE@/gcc-objc-@DATE@.tar.gz">
+ <p> <a href="@LONG_DATE@/gcc-objc-@DATE@.tar.bz2">
gcc-objc</a> @TEXT_DATE@ snapshot, includes just the Objective-C
front end and runtime.
- <p> <a href="@LONG_DATE@/gcc-objc-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-objc-@LAST_DATE@-@DATE@.diff.bz2">
gcc-objc-@LAST_DATE@-@DATE@</a> patch file to bring gcc-objc-@LAST_DATE@
up to gcc-objc-@DATE@.
- <p> <a href="@LONG_DATE@/gcc-ada-@DATE@.tar.gz">
+ <p> <a href="@LONG_DATE@/gcc-ada-@DATE@.tar.bz2">
gcc-ada</a> @TEXT_DATE@ snapshot, includes just the Ada
front end and runtime.
- <p> <a href="@LONG_DATE@/gcc-ada-@LAST_DATE@-@DATE@.diff.gz">
+ <p> <a href="@LONG_DATE@/diffs/gcc-ada-@LAST_DATE@-@DATE@.diff.bz2">
gcc-ada-@LAST_DATE@-@DATE@</a> patch file to bring gcc-ada-@LAST_DATE@
up to gcc-ada-@DATE@.
</blockquote>
-<p>If you are using an x86 GNU/Linux system that uses RPMs to handle
-installation, you may find the daily RPM snapshots at:
-<a href="http://www.codesourcery.com/gcc-snapshots.html">
-http://www.codesourcery.com/gcc-snapshots.html </a>
-easier to install.
-
-<p>Note at times you may find newer directories on the server with limited
-permissions. These represent snapshots that have not yet been verified
-as correct, or are known to be incorrect.
-
-<p>When a particular snapshot is ready for public consumption the directory
-permissions are relaxed, the LATEST-IS- file is updated and a message is
-sent to the GCC list.
-
-<p>Using a snapshot before it's officially made available is an unwise thing
-to do since it may become impossible to update to an official snapshot.
+</p>When a particular snapshot is ready for public consumption the LATEST-IS-
+file is updated and a message is sent to the gcc list. Please do not use
+a snapshot before it has been announced that way.</p>
-<p>Old snapshots can be found on the ftp server
-<a href=ftp://gcc.gnu.org/pub/gcc/snapshots/>
-gcc.gnu.org:/pub/gcc/snapshots.
+<p>Old snapshots can be found on the ftp server <a
+href="ftp://gcc.gnu.org/pub/gcc/snapshots/">ftp://gcc.gnu.org:/pub/gcc/snapshots</a>.</p>
-<hr>
-<address><a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a>
-<address><a href="mailto:gcc-bugs@gcc.gnu.org">gcc-bugs@gcc.gnu.org</a>
+<hr />
-<p>
-Last modified @TEXT_DATE@</address>
+<address>
+<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a>
+<br />
+Last modified @TEXT_DATE@
+</address>
</body>
</html>