This is the mail archive of the
mailing list for the GCC project.
Re: [wwwdocs] Initial criteria.html (was Re: Where's the currentlist of release criteria?)
- To: <gcc-patches at gcc dot gnu dot org>, Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: [wwwdocs] Initial criteria.html (was Re: Where's the currentlist of release criteria?)
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Wed, 31 Oct 2001 17:26:45 +0100 (CET)
- cc: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, Phil Edwards <pedwards at disaster dot jaj dot com>, <gcc at gcc dot gnu dot org>
On Tue, 30 Oct 2001, Gerald Pfeifer wrote:
> If one of you wants to make the changes above, these are pre-approved;
> else I'll try to do it tomorrow from work.
(Obviously, I cannot and do not want to interfere with Mark's work as
release manager; rather, I'm trying to help by resolving obvious issues.)
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.1/criteria.html,v
retrieving revision 1.1
diff -u -3 -p -r1.1 criteria.html
--- criteria.html 2001/10/30 17:41:01 1.1
+++ criteria.html 2001/10/31 16:24:57
@@ -41,6 +41,9 @@ possible.</p>
relative to previous releases of GCC. Each of these improvements must
be completed before GCC 3.1 is released:
+ <p>High-priority open bugs in GNATS will be fixed before the
+ GCC 3.1 release.</p>
@@ -49,15 +52,6 @@ be completed before GCC 3.1 is released:
<li><p>Java Standard Library</p>
-<li><p>GCC Support Library</p>
-<li><p>Java Front-End Garbage Collection</p>
- <p>High-priority open bugs in GNATS will be fixed before the
- GCC 3.1 release.</p>
@@ -136,7 +130,7 @@ behavior will not be a primary considera
not to ship a particular release candidate:</p>
-<li>Chill (<strong>Dropped</strong>; see above)
@@ -144,8 +138,7 @@ not to ship a particular release candida
<p>In particular, no application testing, code quality, or compile-time
performance testing will be required for these languages. However,
the regression testing criteria documented below will apply to these
-languages, except Chill, for which no regression tests are
@@ -153,8 +146,9 @@ available.</p>
well as some Fortran, and Objective-C tests. GCC 3.1 will not fail
any of these tests which the previous release GCC passed on any of the
supported platforms. In particular, the current regression testsuite
-will be run using GCC 2.95.2 on each of the supported platforms; those
-results can then be compared with the output from a release candidate.
+will be run using GCC 3.0.2 and GCC 2.95.3 on each of the supported
+platforms; those results can then be compared with the output from a
Because there have often been issues with generating PIC code, we will
test with <code>-fPIC</code> as well.</p>
@@ -347,13 +341,11 @@ both GCC 2.95.2 and GCC 3.1.</p>
<li>What other tests should we use for compile-time performance
<li>What tests should we use for code quality?
-<li>Should <code>-fstrict-aliasing</code> be enabled?
<li>Should we use flags higher than <code>-O2 -g</code> when
bootstrapping? (Probably we should have a matrix of various flags, as
in previous releases.)
<li>Should we add PowerPC GNU/Linux to the list of platforms?
<li>Should we use Tru64 in place of Alpha GNU/Linux?
-<li>Should we eliminate setjmp/longjmp exception-handling?
<li>Which open bugs need to be fixed?