[m-rev.] for review: add warning about GCC 4.0 to web site
Julien Fischer
juliensf at cs.mu.OZ.AU
Tue Aug 16 02:13:50 AEST 2005
On Tue, 16 Aug 2005, Ian MacLarty wrote:
> For review by anyone.
>
> Estimated hours taken: 0.3
>
> Put warnings about GCC 4.0 on the web site.
>
> download/include/release.inc:
> Add GCC 4.0 to the list of versions of GCC known not to work with
> the current release.
> Remove the comment about GCC 2.7.2 since it doesn't say anything
> useful.
>
> download/include/rotd.inc:
> Remove the comment about stable release of the days being put in the
> beta-releases directory since it's a bit confusing given that the
> beta release is a seperate version.
>
s/seperate/separate/
> Add warning about GCC 4.0.
>
> Change ROTDS to ROTD since there is only one unstable release of the
> day at any point in time and since the capital S is a little confusing
> -- I thought it might stand for "Source" at first.
>
> include/download.inc:
> Remove the comment about a now old version of Mercury shipping
> with an old version of Debian, since it's unlikely to be meaningful
> to anyone.
>
> Index: download/include/release.inc
> ===================================================================
> RCS file: /home/mercury1/repository/w3/download/include/release.inc,v
> retrieving revision 1.34
> diff -u -r1.34 release.inc
> --- download/include/release.inc 6 Jun 2005 03:18:45 -0000 1.34
> +++ download/include/release.inc 15 Aug 2005 14:47:09 -0000
> @@ -125,19 +125,14 @@
> <li> <a href="http://gcc.gnu.org">GNU C (gcc)</a>
> <p>
> We recommend GCC 2.95.*, 3.1.*, or 3.2.
> - More recent releases may also work.
> <p>
> - GCC 3.0 will NOT work. It has bugs which cause internal compiler
> - errors when compiling the C code generated by the Mercury compiler.
> - <p>
> - GCC 3.3.1 will NOT work. It has a different bug which also causes
> - internal compiler errors when compiling the C code generated by
> - the Mercury compiler. This is apparently fixed in GCC 3.3.2.
> + GCC 3.0, 3.3.1 and 4.0 will NOT work.
> + They have bugs which cause
> + internal compiler errors when compiling the C code generated by the
> + Mercury compiler.
> <p>
> Avoid GCC 2.96 (distributed with Red Hat Linux 7.x) and
> other unofficial releases of GCC.
> - <p>
> - GCC 2.7.2 may work, but has not been tested recently.
> <p>
I suggest saying that we don't recommend using any version of gcc
less thatn 2.95.X (we certainly haven't tested on anything less than
that for ages.)
> It is also possible to use other C compilers, such as
> <a href="http://www.cs.princeton.edu/software/lcc/">lcc</a>,
> Index: download/include/rotd.inc
> ===================================================================
> RCS file: /home/mercury1/repository/w3/download/include/rotd.inc,v
> retrieving revision 1.9
> diff -u -r1.9 rotd.inc
> --- download/include/rotd.inc 5 Apr 2005 04:25:40 -0000 1.9
> +++ download/include/rotd.inc 15 Aug 2005 15:04:41 -0000
> @@ -32,8 +32,12 @@
> of Mercury, but would still like some stability, we release a daily
> snapshot of the development system. This is called a "release of the
> day (ROTD)" and is given a version number "rotd-YYYY-MM-DD" according to
> -the date it was built. When the compiler passes all its tests, a ROTD
> -is put into the beta-releases directory.
> +the date it was built.
> +<p>
> +Please note that the stable release of the day will not work with GCC 4.0
> +because of a
> +<a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22362">bug</a> in that
> +version of GCC. We recommend using GCC 3.4.x.
>
I suggest saying "GCC 3.4.x or before".
> <B>Download releases of the day:</b>
> <ul>
> @@ -43,7 +47,7 @@
> Mercury ftp site</A>
> </ul>
>
> -<H3> Unstable ROTDS </H3>
> +<H3> Unstable ROTD </H3>
>
> For some people, the cutting edge is not enough, and they want the
> bleeding edge. To help these developers, we have an <em>unstable</em>
> @@ -51,6 +55,11 @@
> all its tests. It is marked with a version number
> "rotd-YYYY-MM-DD-unstable".
> <p>
> +Please note that the latest release of the day will not work with GCC 4.0
> +because of a
> +<a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22362">bug</a> in that
> +version of GCC. We recommend using GCC 3.4.x.
> +<p>
Likewise here.
> <B>Download unstable releases of the day:</b>
> <ul>
> <li> <A HREF="<? echo $root; ?>/download/files/beta-releases/rotd/">
> @@ -59,7 +68,7 @@
> Mercury ftp site</A>
> </ul>
>
> -<H3> Contents of the ROTDS </H3>
> +<H3> Contents of the ROTD </H3>
>
> The Mercury compiler is written in Mercury, and compiles Mercury into C
> code. These releases contain the Mercury code and the generated C code
That looks fine otherwise. It may also be worth adding a note on the
0.11 release that gcc 3.4 won't work with it (although hopefully 0.11
won't remain an issue for too much longer).
Cheers,
Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
post: mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------
More information about the reviews
mailing list